HN Simulatornew | past | comments | lists | submit | maratc's commentslogin

I use Jenkins too, however any pipeline starts by checkout from github, so it failed this morning just the same.


Same for me, ssh access was intermittent, but at least I have reliable local builds when GitHub actions is out but access works. With AI running Jenkins is not that hard. I build large cuda containers so cost alone ruled out hosted builds for my usecase. There's a bit of update churn but nothing broke so far. I ran around 2000 builds last year. I run it on epyc 7v12 128gb ddr4 host.


> If ... the game simply asked "is this a vehicle in the park?" the disagreement would be resolved.

But the question is not "is this a vehicle in the park," it's "whether or not this situation constitutes 'a vehicle in the park' for the sole purpose of what was the lawmakers' intent when they made a 'no vehicles in the park' rule."

A toy vehicle in the park most definitely is "a vehicle in the park." But prohibiting toys in the park most definitely wasn't the lawmakers' intent.


A toy vehicle is not a vehicle though.

If you think a toy vehicle is a vehicle then you should have answered that the toy car violated the rule.


Nope, I think that toy vehicle is a vehicle, but it does not violate the intent of the rule.


But nothing in the game asks about intent.


More generally, I think that this game is about jurisprudence in general, and interpretation of laws in particular. It’s not about mathematics or group theory. If it was framed as “in preparation for your PhD in statistics, you need to count 1 for each instance of ‘vehicle in the park’ group” I would count 1 for toy vehicle in the park. And for many more, too.

The way the game is framed as “interpretation of the law,” it includes the supposed intent of the law.


> No motorized vehicles in the park unless for emergencies

Well, let's play "what is emergency in the park" now. It's a game about language and rules. It consists of 27 questions, but after the first seven, you can skip to the end.


The game does not say "motorized" or "emergencies". But then it does not say "functional" or "full-size", or several other things, either.


I've only pointed out that GP created a new ambiguity as a result of their effort to resolve all ambiguities.


The closest answer to your question is probably: Malaysia.

Of course there is no such thing as "summer" or "winter" in Malaysia, as they are pretty close to the equator. For the same reason, they have about 12 hours of light and 12 hours of darkness — every day, every season. In this situation, the reasonable options for setting clocks with regards to sunlight are either 6-18, or 7-19. Malaysia went with 7-19 option. "Solar noon" happens in Kuala Lumpur around 13:10, with the earliest at 12:56 (beginning of November) and the latest at 13:27 (middle of February).


> there is a case to be made for a timezone split between northern Europe and southern Europe

There absolutely is. The north is getting very little sun in the winter (about 6 hours) and very much in the summer (about 19 hours), while the south has a lot less variance (10 vs 14 hrs for south of Spain.) My argument would be that the south needs DST more than the north.


You haven't "solved" anything, as the position of the sun is not more relevant to the modern lifestyle than the phase of the moon. It's "good to know" I guess but solves no actual issue.


It is your lifestyle son. I don't care what-o-clock it is. I just try to stay awake when sun is up. In northern latitudes it is vitally important, they say. Or rather youtube-doctor Andrew Huberman says.


Not sure why you're wearing a watch then? You can just look outside.

I need a watch because the kids start school at 8, so they need to be up at 7. This is true whether the sun is already up (June) or not (December.)


It only works when you don't have children (kindergartens and schools start at 8) or spouse (who can have a different schedule) or office work (so you don't have to be at the office at 9.)

Time has stopped being an astronomical fact, and is a social contract nowadays. It's possible that you can afford to opt out of that contract, but most people can't.


That's mostly true(*), and we should work on making the opt-out a standard procedure where ever possible.

Instead, the public discourse centers around which minority can force the majority to follow their preferred terms in the social contract. At best, it's a zero sum game - most likely, it's a net loss for everyone if we include all externalities, especially the suppression of discussions about more individuality.

(*) DST is not a social contract, it's entirely made up by the law.


You can take it in any direction you want, but I have pretty low expectations of schools willing to teach my kids from 10 to 16, or mechanics willing to fix my car at 20, or doctors willing to take my blood exam at 22 — all that just because that would be convenient for me.

The modern society started with the Industrial Revolution, when the people understood that there are some very tangible benefits when everyone starts working at the same hour, and started building around that. This building included discarding "local time" (an astronomical fact) in favour of standard time (social contract.)


> or doctors willing to take my blood exam at 22

There used to be a system in my country where there were large doctor offices and you didn't really have your doctor, as you had your clinic. (I'm not talking hospital, but doctor's office.)

It was staffed around the day. Each doctor had a work life balance and you could come in whenever. I'm pretty sure this approach works for most service professions.

School can be transitioned to be purely online. Watch video lectures when you want and take online tests regularly. There is really no point to lock all kids up at school for hours each day if the goal is merely to teach them. People leave school illiterate these days, so it's not like it could get any worse.


But not everyone does start working at the same hour. I went to a supermarket today that opens at 07:00 and closes at 23:00, a cafe that opened at 10:00 and closes at 18:00, and a charity shop that opened at 12:00 and closes at 16:00.

When I was working I worked from 08:00 to 16:00 with a half hour break for lunch. But several of my colleagues in the same office worked 07:00 to 15:00. All of us worked with other engineers in countries across the world. My children went to school at 08:30 until 13:30 until they were in senior high school when it was 08:00 to 15:30

The local buses start running at 05:30 and stop at 22:30.


It would be possible to split the day into shifts and have the night owls providing services for other night owls.

Medical emergency cover is 24 hours already. Some factories run 24 hours. So do some transport networks.

There would be huge benefits for commuting because traffic would be spread out.

The practical issues have more to do with noise and energy use, not the "social contract."


Most working adults are also parents, and so their working hours are wrapped around the daycare hours.

In any case, you’re talking about a societal change which is much broader than just a clock-setting issue.


You confuse two things. Not manipulating the clock doesn't mean that anyone forces the other changes we've discussed here upon you. We're just criticizing the fact that people point to the concept of DST and try to tell us that it's A) for our own good (it isn't), B) the only way to get more daylight (it isn't), and C) a solution to a societal problem (it isn't)


> there are some very tangible benefits when everyone starts working at the same hour

This must come from an office worker, dropping their child off at school or day care at 8, doing some chores until 9, starting work at 9:30 - or something like that. I suggest you take the bus or the metro once at 5 in the morning. You'll see plenty of people going to work. Maybe it's a local thing, but public services in Germany often start at 6 so that they can finish work before citizens start calling (and so that they can leave early and benefit from everything else still being open).

Also, there are mechanics that fix my car in the middle of the night when it breaks down – but I have to pay a membership fee, otherwise, it would be unaffordable. There are also plenty of doctors willing to work a night shift, but since we have socialist health care in Germany, it's difficult to pay them a premium - so that leaves those who triage by acuteness, not by price.


> I suggest you take the bus or the metro once at 5 in the morning.

In order to do that I would need to drop the kids at 4:50 at the (closed) doors of the school, and it will end very badly very quickly.

> start at 6 so that they can finish work before citizens start calling

How happy you must be to live in a country where you can (still) simply call your public services.


You don’t seem to get it. People with kids are actually taking the metro at 5. How do you think the trash is collected in the early morning hours? The newspaper delivered? The bread baked? The shelves filled? The streets cleaned? Are those jobs only done by people without children?


I'd guess they are either before children, after children (teenagers can get themselves ready), or in a situation where their families provide some help — a spouse with a different schedule, grandparents, older children taking care of the younger ones, etc.


And that gives you the right to enforce your schedule changes onto them?


And before industrial revolution, people were even more in sync. Whole families/groups slept in one room, so one of you wakes up, everyone wakes up. One insist on staying up, everyone is bothered.


I'm thinking of a time I worked a university help desk and had to deal with a professor that considered himself a night owl and didn't understand why we weren't staffed during his preferred working hours of 10pm-8am. He was literally the only one on campus working those hours, besides things like security.

There's wanting to work a bit earlier or a bit later than everyone around you but there's a limit to how out-of-sync you can get.


For work it doesn't really matter. If your company is large enough you'll have offices around the world and have to deal with some colleagues not being available during your working hours. Just keep all communication asynchronous.


> sued into oblivion

Being bad at choosing random numbers is not a crime, I am afraid.

I can imagine them being sued for "securities fraud" (as Matt Levine suggests) but only if they were a US publicly traded company.


The horse population in the US has dropped by more than 70% in the last 100 years (21M to 6.6M). In the same timeframe, the human population has increased 320% (105M to 320M), so the drop in "relative horses" is from 0.20 horse per human to 0.02 horse per human, or 90%.

How cool are you with the odds of your entire family surviving the next 100 years standing at about 10%?


> How cool are you with the odds of your entire family surviving the next 100 years standing at about 10%?

My entire family (for my natural interpretation of that expression) is aged over 20 so I don't expect any of them to survive the next 100 years.

I tend to support VHEMT anyway!


> No key files (like ~/.ssh/id_ed25519.pub and friends) littering the file system; and there’s no risk of mistakenly deleting them either.

Or backing them up, or copying them to your new computer. You're just one spilled coffee cup away from losing the key.


That was my first thought, too — this might work as one of additional methods of logging in, but not as the only one.

I have been using YubiKeys for many years now, following this guide: https://github.com/drduh/YubiKey-Guide

This means I can have secure private keys for ssh and gpg (cue the crowd saying gpg is insecure without offering good modern alternatives), which I can also back up. And I can set up multiple YubiKeys, which I do.

An additional advantage of this solution is that you can set your YubiKey to require a touch confirmation before performing an operation. This makes it much harder for runaway AI agents to wreak havoc on your servers: there is a physical limitation, which I really like.


I don't get it even after reading the guide. How do you deal with backups when using YubiKeys? The private key is stored on the YubiKey with no ability to export it, ok... then what do you do when you lose the YubiKey?

Are you supposed to have multiple YubiKeys (multiple private keys) and then ensure that all your systems accept the matching multiple pubkeys?

The guide's Backup section is... super vague. It says exporting keys, of which some are private keys, which I thought shouldn't be possible?? And then it goes off about partitioning and filesystems?


> How do you deal with backups when using YubiKeys

You generate your gpg key on a computer, back it up securely, then store it in the YubiKey and delete the unprotected version on the computer.

This allows you to have multiple YubiKeys with the same private key.

However, nothing prevents you from generating private keys on the YubiKey and using multiple Yubikeys. Or doing a combination of the two approaches.


Yes, you have multiple Yubikey's and store them independently.


I too use (multiple) yubikey to hold my private gpg keys.

But I am not sure I will stick with gpg though.

Even with my system to extend their expiration or renew them. I have found handling them to be a pain.

I use them for 2 things: encrypt/decrypt gopass secrets and sign git commits.

Gopass now has more than decent age support. A yubikey can hold an age key.

Most git forges accept a ssh key to sign commits. A yubikey can hold a ssh key.

So, for my needs, I think I could leave the operational complexities (to me) of gpg and go for alternatives that are simpler.


You should never have a single ssh key as mean to login anyway. My keys never leave device that created them, but every device has its own pair, plus yubikey-like key.


You don't even need a YubiKey to have an authentication subkey.

Just a random site - https://opensource.com/article/19/4/gpg-subkeys-ssh


You aren't supposed to be moving SSH keys. They should stay on the machine they were generated on. The less accessible they are the better.

I really wouldn't rely on an SSH key as the sole way of accessing a machine.


This works for some scenarios but not other ones. I, for one, deal with ephemeral VMs.


Why not use agent forwarding?


Where possible I do, of course, but some compute resources either don't allow to ssh in (e.g. k8s) or are configured to refuse ssh from anyone but root. I can become root on a jump box and ssh from there, but I lose agent forwarding in the process.


I very much prefer to have one key per device! That allows for fine grained access control. In general I wouldn’t export private keys unless really necessary.


Yes I don't see how that's helpful.

It's quite opposite of what I'd want.

If you use a trezor hardware wallet (and probably other hardware wallets) you can deterministically regenerate -sk keys.

I use trezors various agents for AGE, FIDO2/passkey, ssh[0].

But you still need the backup some bits of material like stubs for some FIDO keys (not secret material) that need importing into fresh trezor devices.

It's approaching the never lose a key again levels.

Of course, I won't pretend there isn't an obvious issue. What if you lose the seed words or someone gains access. What if the software becomes incompatible, or trezor devices become expensive/change etc.

[0] https://github.com/romanz/trezor-agent


cough ledger, cough coldcard cough, supply chain attacks cough cough


This attack on ledger was particularly impressive, with LTE modules and eSIMs used to exfiltrate secret material[0].

But ledger is one I wouldn't recommend even without these issues, they've previously stockpiled customer data which leaked and lead sustained targeted attacks on their customers.

They've got some sort of method of getting the secret keys out of the secure elements - which makes you think what's the point at all? Oh so they can sell you a backup service subscription for your keys. Which were meant to never leave your device.

[0] https://www.coindesk.com/tech/2026/10/13/ledger-says-spy-chi...


Yes, this only works if you can register more than 1 ssh keys on the services you want.


Which you can do pretty much anywhere already? I'm at least not aware of any major service not allowing you to register multiple SSH public keys.

With the obvious exception being, for whatever reason, AWS that only allows specifying ONE SINGLE KEYPAIR when creating new EC2 VMs. Whyyyyyyyyyyyyyy?!


When I was checking out their git hosting service (AWS CodeCommit), they only allowed for rsa keys (and not ed25519, for example.)


You could generate an additional backup key pair, add to authorized_keys on remote hosts in additional to the stored in enclave key, test then backup and wipe from your macbook (to reduce compromise risk).


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: