white-space: pre-wrap;

How about this, then: It fills a niche, but it is full of bad decisions (and fragmentation), and survives mainly by its existing momentum. It's crap in the same sense that Unix is crap: the founder effect has made its flaws impossible to dislodge or rethink.

A popular solution to a problem is not necessarily a good solution to that problem.

There's nothing much to doubt. The evidence is always the same: "our web server logs show scrapers originating from IP addresses owned by someone who didn't pay us."

The Verge article is a little clearer. 100,000 threads pilfered over the past year with scraping! Oh no!

(See also: the actual legal filing. I have to admit the headings sound a little unstable.)

Just you wait—they're way more over-represented they are in subreddit moderators... and in the accelerationist movement.

"Actually" read them? Are there a lot of people running around purporting to have read TSR novels, or to have credentials that require doing so?

Nothing. That should always be used when possible. Read about Advanced Data Protection. It is designed to pass the Mud Puddle Test, where your old device is not available to encrypt anything, while the user has not yet bought their new device.

I worry about that. In my threat model, I assume the attacker wants to keep the backdoor secret, and is unwilling to push a secret mass surveillance backdoor to all phones. Even if no one noticed the backdoor, someone is likely to notice all that encrypted surveillance traffic. So, there may be occasionally used back doors in our phones already, but secret mass surveillance is done server-side. That's the main threat I'm worried about.

Check out the github repo I just created. Simply ask to become a contributor.

Data can eventually add up. It isn't like a block chain, but we might have say 1KiB per device, and 8 billion devices globally, so maybe 10 TiB? That's assuming we don't ever shard into different quorums, and 15-ish nodes run the world, which is probably unrealistic. With say 150 nodes by then, it could add up to 1TiB per node.

Queries per second would always be low. Using a public key for incremental backups and only rotating the private key every month or two, 8 billion devices registering once a month is only 3,000 QPS globally, and again dividing by 10, that's only 300, which a Raspberry PI can probably handle.

So... it's dumb, but I will find it entertaining to run my node on a Raspberry PI until I start having security concerns. That would be roughly when enough devices are enrolled to make the system a juicy target, probably at least 2 years out. We'll need improved security at that point, e.g. running nodes in data centers with multi party with for any changes, and maybe Tor routing.

Anyone interested can ask to join my Github project.

There are no real downsides to saying the 2026 version is 26 and the 2126 version is 126. It's just [year - 2000]; you can even imagine this is release 026 rather than 26. Personally I'd worry more about what happens in the year 3000 when they have to release version 1000.

Moreover—these are just version numbers, imitative of dates, rather than actual date fields. It's not like someone is going to be charged for unpaid bills because their iOS version number was accidentally parsed as being in the past. Take your damn pills, grandma!

And yet you registered on Slashdot. Curious.

(The social credit system isn't real. See here for debunking.)

They kinda did; Diet Coke is based on the New Coke recipe.