For all purposes and intents it's a notably better choice; neater, faster, safer. We are today incapable of producing anything close to the electrical energy required to brute-force even one tenth of such a key's space, and even if we could we don't have computer power that can ingest and use such an amount of energy.

...even 5 years from breaking RSA 2048 with anything quantum. Once there, the way to surpass RSA 4096 is yet longer. If you want to stick with RSA instead of something modern like Ed25519, then move to 4096 bit keys today and you can stop thinking about this at least another decade.

For your actual SSH keys you can stick to RSA 4096 or better still, Ed25519. As for the key exchange phase, which I presume is what you're really asking about, there are two post-quantum alternatives available today: ML-KEM x25519 (aka "mlkem768x25519-sha256" in OpenSSH) and NTRU Prime ("sntrup761x25519-sha512").

No. It's not going to create an avalanche effect. The "singularity" isn't about to happen.

On the whole the number of carriers that have adopted RCS is low, and among those that support it almost none have full support across their entire network. Coverage for RCS is still very spotty and adoption is at crawling speed since years. Source: I work for a telecom services provider, and we still cannot offer RCS-as-a-service because the "reach" is almost none.

They do not have light that's better, or even equal to incandescents. Or halogen. Or fluorescent tubes. LED bulbs' light is "hollow" because they emit only parts of the spectrum. All LED bulbs have a relatively low CRI (color rendering index) which is why items with yellow/orange/red colors appear "lacking" and strange in LED light. Even the upper tier of expensive LED bulbs are still far from a 100 CRI.

One of Google's previous cables (Dunant) has a 250 Tbit/s bandwidth. I'm not so sure this cable is spec'd at "only" 100 Tbit/s.

One of Google's previous cables, Dunant, has a 250 Tbit/s bandwidth. I'm not so sure this cable is spec'd at "only" 100 Tbit/s.

A simple *sh script I wrote years ago that wraps up pre-defined paths, asks for a password, then spits out a compressed and encrypted tar-ball which is kept both locally and uploaded remotely to a separate location.

Snore. You should also post the platitudinal "a fractal of bad design" article while you're at it just to make it look like you know what you're talking about, you non-programmer you.

Who's surprised? In usual order the Chinese govt. is still nothing but a bunch of thieves and liars.

Only 5% of in-shop transactions in Sweden are done with cash; about 95% are done with a regular debit card. I personally haven't used cash more than on a handful of occasions the past 15 years, and cannot recall the last time I saw another custome pay with cash.

Filthy hypocrites.

My noggin' definitely works better, and I become a bit more productive, when having had one or two ~5% ABV beers. It's not enough to make me tipsy but it's enough that something cognitive-wise "clicks" into place... in lack of a better description.

The bug isn't remotely exploitable in the default configuration.