Three states over and back would be a day or two minimum, but potentially nearly a week on the west coast. (Depends on start and stop locations obviously, but if you start from eg Portland, three states over could be the Dakotas).

From a technical perspective, it doesn't seem to be _that_ difficult: it seems like KYC but for anyone who wants automated access to telephone networks. I know there are some existing efforts there that are more technically comprehensive than that (SHAKEN/STIR), but I don't know where they're at in terms of adoption/rollout.

What’re the actual, practical results of a package pushing you towards a higher go version that you wouldn’t otherwise have adopted right away? Why is this actually important to avoid beyond “don’t tell me what to do”?

Can you please elaborate on this? I've seen this argument from others as well, but nobody has ever been able to articulate what that actually looks like and why rebasing branches specifically is to blame.

My perspective: whatever happens to the commit history on your non-`main` branch is your business. I don't care about the specifics until your work is merged into a shared branch that we all understand to be the canonical representation of the software we're working on.

Comments URL: https://news.ycombinator.com/item?id=47355671

Points: 3

# Comments: 1

Gonna be honest, it has taken away from the message both times I've seen it. It feels a bit like you're LARPing your favorite humans vs robots tv show.

> In practice, pornography showing genitalia and sexual acts is not ipso facto obscene according to the Miller test.

I'm not sure you can make the statement that pornographic materials aren't protected speech. I don't think you can make the statement that they are though.

bombcar said "They're quasi-generated with random elements and fixed elements - similarly to early Diablo procedural generation." (which is true - you confirmed as much in the very next comment - "The levels are all hand drawn, not generated by an algorithm, even if they’re shuffled.". That's all early Diablo was doing.)

"Quasi-generated" seems like an appropriate descriptor here - stringing together level building blocks algorithmically is still "generating" a level in a sense. You're right - it's not correct to say that they were generated in the same way that an LLM generates things, but a) nobody claimed that and b) there is an undeniable element of procedural generation here.

I did not claim that it was the same security scheme or that it's biometric or anything like that. I did claim that you have to physically touch it to activate it.

Edit to add:

re 'Yubikey Nano is a "thing you have", TouchID is a "thing you are".', I would argue that your finger is in fact a thing you have. The loss of a finger might change a little of who you are depending on the circumstances that led to you losing said finger, but these both fall into "thing you have" territory for me. I don't think it's wise to consider Touch ID much more than that, personally.

There's nothing in that press release that implies that the memory was somehow different (or "consumer-grade"). The _only_ thing they're saying is that they're ending their B2C business and focusing on B2B.