A simpler explanation could be wanting to skip the print->sign->scan ceremony required by some institutions.

I'm sorry, but that's silly. The argument is the other way around: would you like to be stalked by an airtag?

You can be stalked by 100 different devices on the market though. Not like this is the only possible way to track someone.

This is like nerfing knifes because they can kill people.

Firefox on Fedora 43 here, no joy, and indeed, randomly broken on Linux (too).

[edit] Okey, so installing the complete Google Noto Fonts family resolved this issue. But I still don't know if relying on a script with almost no font support is any better than what the OP did.

The next gen is semantic and sentiment filters, the age of wordlists is over.

What they probably meant was writing 'import "file.ts"' and have tsc emit 'import "file.js"'. https://github.com/microsoft/TypeScript/issues/49083

Given the context of Node here will allow experimental type-stripping and will not be doing things like import rewriting, Typescript's decision here to focus on "users write .js in imports because that's how the type-stripped file should look" seems like the right call to me. Less work for a type-stripper because Typescript can already check if there is a .ts or .d.ts file for you if you use .js imports everywhere.

"AI" had no issue pirating books (books3 and all that).

If your blog is readable by and interesting to humans, it will be exploitable by leeches.

It's more like stack based event propagation.

Timestamp with time zone is the type for an "absolute timestamp".

Timestamp without time zone is for local time, and sometimes abused as "time in utc without being explicit about it".

The naming describes the expected input, not what is stored. The time zone name or offset is not stored with timestamptz.

Always use timestamptz, unless you have a specific use case for local time.

Yes, it is quite confusing and I dread to think how many have got it wrong and store local times like the GP.

But it's also not as simple as "always use WITH TIME ZONE". That also leads to a mistake.

The reason is (just to reiterate what you said) the TIMESTAMP WITH TIME ZONE does not store the time zone! If you ever want to get local time back (e.g. ask a question like "how many users log on before lunch time") then you need to store either local time in a TIMESTAMP WITHOUT TIME ZONE field, or the time zone, and get local time like: SELECT recorded_at AT TIME ZONE time_zone AS local_time ... (I prefer the latter).

You could allow to pair the part to some central control unit, when the car is unlocked. I don't speak car or cryptographer so so I have no idea about how to go about it, but this seems like a workable solution.

Discord is one of the last widely used, user-friendly messaging platform, that doesn't require phone number verification at sign-up.