And extracting a fuck tonne of sensitive data

Hell yeh!

I'm amazed it's France before Germany.
But I'm also so happy that this is happening.
The greatest war in history and all the horrors behind it should never be forgotten/hidden/suppressed/rewritten.
Everyone commited atrocities in that war. Nobody is without stain.
Document it all, and make it all widely available

Excel is often used by people that don't know what a database is, and you end up with thousands of rows of denormalised data just waiting for typos or extra white spaces to fuck up the precarious stack of macros and formulae. Never mind the update/insert anomalies and data corruption waiting to strike.

I have a passionate hate for Excel, but I understand that not everyone is willing to learn more robust data processing

It's like "I have a windows computer, I install software on it and use the software. Why would I need more than 1?" Turns into "ooohhh, computers are great. All the things I can run and host. Software isn't just a gui".

It's like learning to love computers again

Not a concrete expert, but dead bodies. They decompose, can create pockets of pressurised gas, and leave a hollow cavity of no structural strength.

Source: Me. I made it up, but seems plausible.

It is not normal to speak to a real person at Google, no

Worth reading the article, but for the TL:drs and comment readers:

• A patent attorney has narrowed down the list of potential candidates that could be central to Nintendo's lawsuit against Palworld developer Pocketpair to 28 patents.
• Out of those, one particular intellectual property describing creature-capture mechanics was labeled as a "killer patent" that would be difficult not to infringe when making a game with monster-taming elements.
• The said property is part of a recently approved patent family consisting of three more patents, all of which were approved mere weeks before Nintendo and The Pokemon Company sued Pocketpair.

The first round of tools for any hobby or DIY project.
If you don't know what you want from a screwdriver, snips, circular saw etc. then there is no point in buying the super primo bells & whistles expensive stuff.
Once you've used a tool and learned what you don't like about it, or what you actually use it for, or how often you actually use it... Then you can make the informed decision to just buy another cheap one, or splash out on something that's actually fun to use.

Buy the 2nd last tool you will ever need.

There are rare occasions where "buy once cry once" apply. But it's rare

Good.
Governments should run their own mastadon instances, and provide official accounts for all their public servants, staff, whatever they are called, as well as an account for each agency.

But quitting twitter is a good first step

Sqlite is a great embedded database.
If you are storing lots and lots of information in a JSON file, CSV file, or coming up with your own serialisation... Chances are, sqlite is going to do it better.
I know loads of android apps use sqlite for storage. I've also managed to open quite a few programmes "proprietary" file format in sqlite.

Postgres has a useful extension, pg_safeupdate

https://github.com/eradman/pg-safeupdate

It helps reduce these possibilities by requiring a where clause for updates or deletes.
I guess if you get into a habit of adding where 1=1 to the end of your SQL, it kind of defeats the purpose.