It's for the greater good, but it's also somewhat against the intention of the law, IMO.
Dataprotection is meant to give users control of their data. A restriction like that takes away a bit of my control, however, since it prevents me from doing whatever the fuck I want with my data.
But again: greater good. It also protects people who don't know what they are doing.
Some idiots keep using one of my email adresses for god knows what, ending up in me receiving newsletters and shit. Since actual user accounts are associated, I typically recover the password (since its my email adress) and then delete the account.
There are a few websites with similar restrictions though. They are completely fine sending shit to email adresses they never bothered to verify, but reject logins from countries (or even US states!) that they don't want. Morons.
The only downside (in comparison to fuel burners) is complexity. Heat pump systems are extremely complex with a lot of parts that could get fucked up over time.
A gas furnace is as simple as it gets with almost no moving parts. Coal/wood furnaces are a bit more complicated if you don't want to blow 100% of the emissions into the air... you need good well maintained filter systems. But it's still far less complex than a heat pump.
So I understand the appeal of furnaces. Simpler systems are easier to understand, are harder to break and easier to repair/maintain.
I think that problem is tackled too rarely in these articles. If you can't take away the fear that people will have a higher upfront invest and higher maintenance costs and higher failure risk, that makes it too convenient to cling to what they know and understand.
But the thing is: B2 is cheap for storage, but retrieval and traversal are very expensive. And if that happens transparently on the filesystem (because you accidentally run grep or the service in question regularly hashes the files or something), you would implicitly download everything stored. And IIRC retrieval costs ten times the storage costs... each time.)
What's your use-case? What do you want to achieve?
Using blob storages as filesystems doesn't work well and could - with B2's pricing structure - became excessively expensive. Blob storages are designed for easily writing and reading individual blobs. Filesystems are designed for random access, listing, traversal, etc.
Sure? It certainly detracts bots that now don't discover the SSH port anymore. Against a targeted attack it's less useful, but that is a very hard problem in any case. If someone is out to get you specifically, it will be a tough battle.
It looks like docspell might even be heavier than paperless-ngx, given that I need to spin up at least 3 JVMs.
Thanks for mentioning it anyway; don't get me wrong. But my current quest is for a lightweight solution.
Current contender might be SeedDMS, but it's a more generic DMS, not so much focused as paperless-ngx. I miss the gallery view, for example.
Rewatching Fringe is always an option.