https://itsfoss.gitlab.io/post/understanding-the-linux--usr-...
`man file-hierarcy` defines modern Linux filesystem layout.
https://www.man7.org/linux/man-pages/man7/file-hierarchy.7.h...
Also the first URL is serving me scam popup ads that do a crap job at pretending to be android system alerts. Next time please try to choose a more reputable source.
This super aggressive OneDrive shit is also why I've stopped putting most things in the standard folders and now just have my own alternative hierarchy in %USERPROFILE% instead.
At least it seems important on NixOS, I had to rewrite a few shebangs on some scripts that used /bin/bash and didn't work on NixOS.
The problem with PGP is that it's a Swiss Army Knife. It does too many things. The scissors on a Swiss Army Knife are useful in a pinch if you don't have real scissors, but tailors use real scissors.
Whatever it is you're trying to do with encryption, you should use the real tool designed for that task. Different tasks want altogether different cryptosystems with different tradeoffs. There's no one perfect multitasking tool.
When you look at the problem that way, surprisingly few real-world problems ask for "encrypt a file". People need backup, but backup demands backup cryptosystems, which do much more than just encrypt individual files. People need messaging, but messaging is wildly more complicated than file encryption. And of course people want packet signatures, ironically PGP's most mainstream usage, ironic because it relies on only a tiny fraction of PGP's functionality and still somehow doesn't work.
All that is before you get to the absolutely deranged 1990s design of PGP, which is a complex state machine that switches between different modes of operation based on attacker-controlled records (which are mostly invisible to users). Nothing modern looks like PGP, because PGP's underlying design predates modern cryptography. It survives only because nerds have a parasocial relationship with it.
Anyone working in government, banking, or healthcare is still out of luck since the likes of Claude and GPT are (should be) off limits.
It's 2025 and C++ modules still aren't suitable for real world use yet despite being standardized 5 years ago.
Additionally standardize the ABI up front so that different compilers can interoperate. Make namespaces native to the object file format.
Also, explicitly standardize a compiler optimization mode that does not try to exploit UB in eldritch ways that break basic assumptions about how the machine works for 1% performance gain. I get that's an undecidable problem so it's ok if some extra annotations (call them "attributes" and write them [[like this]]) are needed here for explicit optimizer hints.
https://en.wikipedia.org/wiki/NaN
Also you even have different kinds of NaN (signalling vs quiet)
If drawings overall are anything to go by it varies greatly by legal system, but most would lean on "yes".
A generated image would most likely be not made locally, so there the added question of the image being understood as "distributed".