SciPiTie

My base opinion is flexibility. You blamed first Linux then Wayland now you’re what about AMD… What’s YOUR point?

You can stick with windows and Nvidia your whole life all I ask is not spread your bullshit from your OP.

See and that’s what’s backwards from my point of view. Even though I was on win mainly back then I refused to buy Nvidia because of their shitty practices.

I’m talking about your and my behavior not about anyone else. :)

The cause is what should matter because that’s what could influence future decisions.

And there is no Wayland mandate anyway so I don’t understand that side of the argument either - there is no “Linux” in this room who decided to switch…

How the narrative has turned Nvidias active sabotage into Linux maintainers fault is beyond me.

Latest for their reluctance to act on scalpers it should be transparent what you’re getting into with Nvidia.

And then people like you write thing like this… Why?!

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.

Not saying that I’m jealous or anything but… I am. Please insert here a personal insult that would offend you adequately!

I have several bank accounts and at least here they all use their dedicated app for mandatory 2fa - Bastards…

And yes, literally: don’t want to use our app? Don’t get an account with us!

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!

“muddy waters” is a saying, I don’t think you should take OP literally. The Rest you’ve written seems to agree with their sentiment btw.

Do you have any context links? That sed looks like something I’d do after 20h not finding the issue at first glance…

I absolutely second logseq. Would you mind elaborating why/how you use notesnook in addition?

Thanks in advance!

I absolutely second logseq. Would you mind elaborating why/how you use notesnook in addition?

Thanks in advance!

There is literally not one singular(!) arr that does what you’re claiming, at least that I’m aware of. The indexing is done by a different thing than the tracking and the downloading.

That’s why you end up with 16 of them like OP after all…

One more thing that people tend to overlook is their closed firmware. If you want to extend or don’t want to go over their servers for remote things than this should be taken into consideration.

It’s literally the only downside I’m aware of though so if that’s not a concern for you then you’ll be really happy with the machine from what I’ve seen with other people,