I don't know.

• I don't need formatting but it doesn't get in the way either. So I am not bothered by it.
• Also pdf and especially PDF/A standard is widely used for archiving and compliance regulation concerning archival and preservation.
• If you want text the same tactic goes: just export in bulk to txt instead of pdf

My main point is: Why would you want a mail specific stack of hosting, storage, indexing and frontends? If it's all plain text anyway so the regular storage solutions for files come a long way.

There is an entire industry (which has its own disadvantages) to get communication artefacts out of those systems and put it in document management systems or other forms of file based archival.

For a moment I thought it was ... Cad Bane ... Sorry not sorry 😁

It seems like a no-brainer but actually no.

Quick test would be for example if there are:

• at the beginning of the music library a lot of "no artist name" "no album name" entries, so the foldername isn't used at all.
• a lot of artist with their own entry with just one album and one song because the actual albumartist collaborated on one song with them and the mp3 resides in the same folder but they got split in the library.
• if the player doesn't show music which isn't part of Playlist.

So my conclusion is their are even 3 types and corresponding mangement:

• Folder based requires file management
• Meta data based requires tag management
• Playlist based requires Playlist management

Often players make combinations also I guess.

I don't know, but I guess the reason why it isn't done yet is because nobody perceives it as a problem. It would require a repository plugin to install plugins I think. But it all comes down to plugin distribution and deployment. Mostly if you want something outside the default repository you can just upload it to your own install / stack. If a developer provide alternative download ways. Like a github release for example.

Can only be done by default ... also means there are other options.

Matt disappoints but their plugin repository isn't a vendor lock in like Apple denying other app stores (without acts enforcing it etc).

If an historical timeline uses this labeling system it can't omit the NT part though. Windows NiceTry came out in 1993 but also long after that MS had MS-DOS based editions (up until Windows Me iirc)

"Any form of NFC payment will not work" means not only Google Pay, but banking apps with their own NFC implementation neither?

Also just to add: Using an Oculus Quest (at least without the "for business" variant) for work related use cases within EU poses risc for:

• business continuity when used with fake Meta accounts to have a kiosk mode and rotate devices among personnel
• GDPR because Meta doesnt sign proper DPA’s

Material visualising or describing FHS can be credited seperatly.

yeah I know

it doesnt close a changeset after every single change, at least it shouldnt. mmv but if I close the app for some time it bundles my changes in one OSM set

Abode with that logo ... At a first glance I thought it was an April's fools joke. 😁