SAI_Peregrinus

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.

Practical upper bound is closer to 35°C, at 100% relative humidity. Or equivalent wet bulb temperature for lower humidities.

Even in an infinite universe there's no requirement for all events to have non-zero probability of occurring. A simple analogy: there are infinitely many integers, but even if you could pick between them all uniformly at random infinitely many times you'd never pick π. Not all events even have to be in the distribution of possible events.

That's often not going to be relevant for evolution, since the distribution covers physically realizable events like adding DNA base pairs.

Crater is one of the biggest benefits of crates.io being the biggest Rust package registry. Being able to test toolchain changes against all the largest crates before those changes stabilize is an enormous benefit.

Jittered exponential backoff. You don't want the whole herd to come back at the same time, you have to add timing jitter to the clients.

Parentheses, commas, em-dashes, footnotes, endnotes, and starting new sentences can all be used for interlocutions.

Endnotes maximize disruption, the reader has to turn to the back of the book to find the end note, then return to what they were originally reading. These are best reserved for citations or similar items where the added information is irrelevant to normal reading. Endnotes can have their own endnotes.

Footnotes aren't quite as disruptive as endnotes, but they're close. Footnotes can themselves have footnotes.

Surrounding an interlocution with two copies of the same character, whether a comma or a dash, reduces clarity —or makes the work ugly— when there's more than one interlocution in a sentence.

Parentheses allow nesting, don't disrupt the flow of reading the way footnotes or endnotes do, and don't reduce clarity with multiple interlocutions. It's generally much better to not have multiple interlocutions, as they inherently make the work hard to read. It's especially difficult to read nested interlocutions. But sometimes nested interlocutions are used to good effect, such as Terry Pratchett's humor involving footnotes of footnotes. Parenthetical interlocutions to define the first use of an acronym or initialism are also a good exception to the rule of avoiding multiple interlocutions in a sentence.

Yep, it's Murphy's law of online content. Anything you want to reference later will be gone, with no archive copies. Anything you want deleted will be available forever.

It certainly can be a good thing! But it can also be considered a bad thing that you have to keep taking them, and have to keep paying for them forever. A one-time fix (a cure) can be more desirable than a lifelong treatment regimen.

SOC2 requires a company to write policies in a large number of areas, and to demonstrate that they're complying with the policies they wrote. AFAIK SOC2 does not require anything meaningful about the actual contents of the policies, nor does it require the policies to remain constant.

I think they mean they're drugs you have to keep taking forever (for the rest of your life) to keep the effects.

It's not just down, it has errors. Not merely some, but elevated errors across all models.

By "runny scrambled" I mean a folded omelette with a runny center, just-set exterior, and no browning. Classic French style, not just slop on a plate.

I do French-style omelets in a carbon steel pan, on an electric cooktop. Mine's an 8.5" omelet pan, perfect for two egg omelets. I treat it a lot like a wok: heat up until a bit of water dropped in shows the Leidenfrost effect, dump out the water, dump in oil, let it smoke for a few seconds, dump out the oil, then reduce heat, add butter, and drop in the (pre-scrambled & strained) eggs & start mixing while moving the pan back & forth. As the eggs start cooking through, begin rolling by folding up the side & back over, once fully rolled slide onto plate.

This takes practice. I made an omelet a day for a bit over a month to get it to the point I could make one perfect every time. The first few were garbage, after about a week I got a decent result, and the rest was just refining my heat control to get it correct reliably.

Runny scrambled (French omelet) isn't too bad on carbon steel IME. And certainly possible on cast iron, since that was the type of pan used when Carême wrote his cookbook. By Escoffier's time carbon steel was more common. Neither of them is famous for having invented a time machine, both predate non-stick cookware, and they're the most famous French chefs in history.

To add (and agree), if you've got (say) a 10-word Diceware-style passphrase with ≥128 bits of entropy, the point of a KDF becomes solely for the domain separation that KDFs provide. That's not particularly relevant for the USB drive case, but it's very useful in the general case of deriving keys. If I'm writing encryption software for my own use where I know I'll be generating a secure (≥128 bits of entropy) passphrase, I just use HKDF or Blake3's KDF mode.

Not all providers tread dots and plusses the same. Gmail ignores dots (strips them out), and omits a plus and anything after it. Some providers include dots, so stripping them will be a different email address. Same for plusses and the content after them.

Schemes like this just indicate they've joined the USB IF.

On the plus side, in electroplating the positive ions are what actually moves. So in the experiments where you can visually see something move from one terminal to the other the conventional current direction is obviously correct.

Name it `-->result.txt`

They also believe in eternal torture as punishment. If someone doesn't accept their god, their god will send that person's soul to hell to be tortured forever. Therefore, essentially anything can be justified to force people to accept their god, since no finite amount of harm can exceed the infinite torture of hell.

People who believe that sort of thing are, IMO, extremely evil, and worshiping an evil deity.

Nearly every bug is at best a denial of service. If the service worked as expected, there wouldn't be any bug. CVSS considers any denial of service a security issue. Therefore, all bugs should have CVE numbers. The Linux team took this to heart, became a CNA, and assigns CVEs to pretty much every bug.

This is why I like to keep the concepts of "config" and "plugin" separate.

How would that work? If you only pay for one day, your access (read and write) gets cut off after the first month. Then if you don't pay the bill for the entire grace period, your data gets deleted.

> and they also imply deleting all your data so that you don't pay for storage.

Not necessarily. They could imply that your storage becomes inaccessible immediately, but only gets deleted after some time period (say, 1 month). What spending limits do depends on the implementation.