SciPiTie

Ahh g I don’t use paperless as an exclusive document storage but as a pure manager. It searches and tags but doesn’t have exclusivity over any files but it’s own indices!

It doesn’t provide more value than jellyfin in that regard - make it visible and accessible.

Worst case I have all my OCRed documents as raw files which I can migrate to whereever.

Files still exist. For my case encrypted as well. My backups roll on the data, not the container.

But I’m not trying to convince you, I tried answering the questions :)

And two answer your last question clearly: I survived before paperless, I’d get along without it. I find a new tool to mitigate my manual labor as good as possible - if that’s not possible then jo harm done. I know I’m flexible, I can learn new tools and I’m never vendor or tool locked-in. I have a high level of self confidence when it comes to my tool chain and how I’d adapt any part of it - from password manager to cloud storage and my mail flow.

To be honest I couldn’t self host anything if I’d had the fear of being lost if a tool is discontinued.

For me it was a few hours wrapping my head around how paperless ngx works and its setup. I had a folder structure as you described already on my Nextcloud so I just configured paperless to observe it for new files.

Where I spent more time then reasonable with was the tagging - you can automate it based on… Well everything.

Now I just let it suggest me tags based on my existing documents plus add a NEW tag to the ones I’ve never reviewed. That’s just a reminder for me though to review tags when searching, I don’t actively re tag new uploads.

If you have a docker environment I suggest just pulling a container up3, throwing all your documents in it and see if it would save you time or cost you time. Would be an hour well spent!personally the OCR alone is it worth it for me - my country still loves paper letters and being able to copy text out of that is awesome (IBAN, account numbers, etc - all the stuff that’s suspectible to typos).

The three letters OCR, tagging, fuzzy search and ease of use are the ones for me.

I never needed the date for a letter but quite often its context for example.

Your suggestion just digitalizes physical folders. If that’s enough for you ok - but you’re missing out.

Just curious is there any recent quantitative source to this? That statement was “common wisdom” already 20 years ago - 10 years ago I decided to just give it a try - and had issues three times in ten years, all three with missconfigured exchange servers.

And I’m not with a high profile provider either.

Just to make sure: I’m not claiming that you’re wrong, I’m simply curious on how lucky exactly I got!

Ohhh now that is awesome and makes sense! Thanks a lot for that find :)

But when I mount a shared /usr on a remote machine it will always have the mount point /usr/local as empty folder - and either have an empty folder or have a mount target that is dependent on a network resource - that’s why for me it’s so unintuitive.

But then again I started with network stuff way more than a decade after all this got created 🤣

This is really helpful, thank you!

I never understood why the shareable /usr is parent to the non shareable /usr/local. Wouldn’t a /usr/shared be way easier especially in the early network days?

If anyone has a link or some insights into this historical nitbit I’d highly appreciate it!

Disclaimer: also Hobby person but did some more reading on that topic in the past. . Think about what those things are then decide:

The tos are your conditions: I as provider of this service will reserve the right to x. When a user does y I will do z. It’s cover your ass for businesses.

A privacy policy on the other hand might be required by law as soon as you process user data in any way. This is something that I would look into your jurisdiction and their requirements. I’d guess Germany is more on the formal side on things (clichés and everything)

In short: you don’t need a tos but most likely want one. You don’t want a privacy policy but most likely need one. :)