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.

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!

“try to be a decent human being to others” isn’t exactly the embodiment of corporate culture though.

I don’t see the need to degrade others to get my point across - and I couldn’t care less if anyone needs a fucking curse to get their shit across.

I apologize - it wasn’t my intention to imply that at all! Emotional self management is a critical skill for managers - and that shouldn’t mean “go away, emotions!”. A trainer and coach I highly respect phrased it simply: “emotions are. They exist if we like them or not.”.

What I intended to convey was “do not use a public platform to channel your emotions.”

If this would’ve been a private conversation I would integrate an explanation of my current situation, feelings and context for my reaction. And also this sounds abstract it can totally be a “dude I’m absolutely pissed. I need you to work with me through this.” (this works btw in both meanings of “pissed” ;)).

Oh that was in purpose! It shouldn’t matter that I personally am angry. My employees should never NEVER try to prevent me from being angry but focus on doing the best job they can.

That’s what I admire about Linus: he realized the negative impact his anger had on the performance of others - and fixed it!

To be clear: I can be angry - but my anger isn’t the reason I want things to change. Being angry is MY FAILURE as manager!

Think about it in another way: do you want your colleagues do things they thin prevent you from being disappointed, frustrated or angry - xor do you want then to move your collective goal forward no matter what you’d think.

Another example: if I’d be the one to have caused this communication mess I’d want my employees to call me out - even though I will get angry the moment I realize I’ve fucked up big time!

As many seem to have overlooked itb this is from more than a decade ago.

And to those setting “not being toxic” == “being vague”:

Suggestion if you’re in a situation: separate the subject discussed from the person and, to the contrary to what is said in some other posts, be very specific!

Improvised example:

Hey all,

patch xyzz and its aftermath communication is unacceptable.

It’s content is not to the standards we have set here (explain).

Even worse, in the communication aftermath we blamed behavior of user space applications for bugs that are within our domain instead of owning up.

The bugs within the kernel will be focused on with highest priority by a, b and myself.

For the communication: (consequences). As explained the patterns shown here are unacceptable.

I have decided to no longer have x as a kernel maintainer on our team/enforce pairing for all communication/set up stricter consequence catalogue. Any specific action,really…

Not perfect as it’s very early here, I haven’t slept well and I’m not deep into the topic.

Just remember to separate subject to be discussed from person(s) acting please.

And always remember: bad communication is really easy and a lot of managers trained that their whole life! ♥

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. :)

“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.

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…

The router is not directly involved in a dns query except, we’ll, the routing if it’s an non local IP. The DNS ip addresses is propagated either via dhcp together with the clients or directly configured in the client. That said: most routers serve as dhcp server at the same time. Perhaps your router is configured to always provide your ISPs DNS as primary.

How the client handles the decision which to query I honestly don’t know and I guess that’s why you and I made different experiences!