SAI_Peregrinus

And when it only sells to government customers.

Tautologically every bug can legitimately be assigned a CVE, since every bug prevents some feature from working as intended. It's therefore a denial of service, which by the definition of the CVE system using CVSS means every bug is at least a 1/Low level vulnerability to CVSS v4.0.

If you're willing to stretch, missing but planned features also deny the use of said features since they haven't been added yet, and so are CVSS 1/Low vulnerabilities.

Resume-driven development for security researchers has never been easier!

> Git hashes are not supposed to be a security mechanism.

Commit signing indicates otherwise.

Also branch names are extremely limited in what they can describe.

Total ego death is impossible. We still have to argue about flakes.

> you have to assume everything you put out on the internet never goes away

Only applies if you regret posting it later. If it's something you want to find later, it will inevitably have bit-rotted and not been archived.

I love how perfect the word "sandbox" is as a metaphor for the security controls they have. A sandbox is a wide, shallow box filled with sand for kids to play in. Even toddlers can crawl or step out of one on their own, it doesn't contain them at all without an adult constantly watching. Kids only stay in a sandbox if they're having more fun playing inside than they think they'll have outside it. AIs only stay in a sandbox if they're having more success inside than they think they'll have outside it.

They gave it access to the internet, so how can that incident prove it's not as clear cut?

Lack of a feature is a bug. After all, it's intended functionality that doesn't work!

It's also a denial of service, since the feature doesn't work yet, and thus should get assigned a CVE.

Peofle often complain that Trump is a "Russian asset" when he's done far more to boost China's success than Russia's.

No, religion requires faith. Faith is belief without or in direct contradiction of evidence.

The same way you recover any other deleted data for which you didn't make a backup: you don't. You eat the loss & make new accounts. Then you remember to make and test backups for the future.

Even if they had customer support, if that customer support had a backdoor to unlock your account it would be regularly used by malicious parties to steal people's accounts & data.

Tools like Pangram can detect whether text is written by AI or a human with a probability non-negligibly different from 0.5. Therefore, the Turing test in its strictest form (that there must not exist such a distinguisher) has not been passed.

Yes, because you don't have to pop in order. "zoxide <subpath>" is "search the history of working directories for a path ending in <subpath> and cd to that".

I remember when the Pause key did that! It's long enough ago that I don't remember which systems did so, and most laptops don't even have a Pause key any more, but it was often very handy for reading fast-moving console output.

Or you can start typing and press up arrow to search with that. Atuin (or some Zsh extensions, etc.) fix the bad UI of having to remember a different key for "search history by order and text" and "search history by order".

Beauty has a function in improving the emotional state of people observing it. Ignoring this function in favor of all other functions can result in getting trapped in a suboptimal local maximum, where a more beautiful design could sacrifice only slightly in other domains and have a greater overall utility.

Aesthetics have a function though, so ignoring them and focusing on all other functions when creating the form can decrease the total functionality.

I didn't say it was a good national ID system, I said it's the closest thing the US has to one.

In the USA they already take passport photos. Being able to receive mail addressed to a name is the closest thing to a national ID the USA has. They're already depended on for identity verification quite a lot.

1000 Colonial Farm Road, Langley, Virginia, United States of America seems likely to me.

I use wire cutters. Non-compliant cables get cut & discarded. I've got a dedicated USB condom with USB-PD support for cases where I want to block data, since those are always charging and I want the negotiation to work for fast charging.

AI safety efforts from OpenAI and Anthropic are purely about brand safety.

ECC allows greater security for key exchange (because it is so cheap to generate keys we can have "ephemeral" exchanges and forward-secrecy). It isn't significantly better for signatures in most cases.

I've got one as well, and I'll say it's extremely nice for removing splinters. I do a bit of woodworking, so it ends up being unexpectedly dual-purpose.

I will say it's important that the soldering iron be temperature controlled. It's especially nice if it's one with the temperature sensing integrated into the tip in a cartridge (like the ones you suggested).

Also, 63/37 tin/lead "eutectic" solder is the easiest to use. Wash your hands after using it, or wear gloves. 60/40 solder is almost as easy, and cheaper. Lead-free is more difficult, especially for learning. Learn with lead solder, then switch to lead-free.

I like to delete all AI comments, and write my own. If I can't write a comment, I don't understand the code well enough to have my name on the commit. I often delete the resulting comment, because AI likes to add many more than are necessary.

If they isolated themselves from all news, social media, and lived as a hermit, yes. They could care less, but it'd be difficult.

IMO JJ allows a simpler "mental model" than git.

Git is a DAG of commits, each of which is a node in the DAG. There's also a staging area that isn't a node in the DAG, and a working copy that also isn't a node in the DAG. The head nodes of every branch in the DAG are always named in git, and every node in the DAG also has a description. Nodes are immutable, but the edges between nodes are mutable so you can edit a node by replacing it with a new node & updating the edges.

JJ is a DAG of commits. Each commit is a node. Nodes have stable identifiers, automatically generated. Nodes may have descriptions. Nodes may also have names (bookmarks) which get used for compatibility with git's branch names. Nodes are mutable, but by default nodes pushed to a remote will be immutable.

> a public example of an open source project that you are using that showcases those features?

IMO that's almost fundamentally impossible. The whole point is that it makes maintaining a "clean" linear commit history easier than git, so by the time you push anything the observable differences are already gone. At best you just see a repo without any WIP-style commits, which can be done using more effort and git alone.