You have several long and comprehensive answers so please allow me to add an emotional one:
Fucking compile error in hour six of what you estimated to be a four hour compile job because of a mistake you made that you found within 5 seconds after the error!!
Fucking why doesn't this compilation start I can't find my mistake for hours?!
Where does this module come from?! What do you mean "root kit"? Learning was fun!
It all was fun! :)
Is there anything to support this? I couldn't find anything that really has this intend documented and Intel weren't the only on pushing for usb as the most simple protocol possible ( I recall a lot of excitement about the "u" part.. How naive at least I was back then!).
I'm not knowledgeable enough to really argue against it, looking simply from an Okham point of view as "they wanted everything to connect" - the printer in the same way as that PDA.... Plus Intels de facto (IT) world domination at the time it just seems unlikely.
Edit: some sentences didn't make even less sense, fixed.
Cups
linux printing server - if you want to share a printer over network or just use one locally on a linux machine.
(not OP but same boat) Doesn't really matter to me because google knows my servers external IP which is a non-issue: I don't expect google to try to attack me individually but crawl data about me. There is no automatic link between my server and my personal browsing habits.
In terms of attack vector vs ease of use , self hosting searxng is a nobrainer for me - but I do have an external server available for things like that anyway so no additional overhead needed.
Two more things to add: you get downvoted not for the content but for the tone. People tend to not respond well to abuse, even if verbal - and at least I read a "make this shit work for me" in between your lines.
And more important: what you are asking is not easy. Wouldn't be on windows, wouldn't be on macos (disclaimer: I've never set up the arr stack on either but docker runtimes) . You are diving into server software no matter if you're the only user or not. Either you accept this and the learning curve ahead of you or you give up on it.
Thanks for the clarification! A wish you an awesome start into the week :)
Preventing teenage pregnancy by obfuscating sex has the same idea.
I agree with the boundaries part. The second part though: they will figure it out either way... At least my brother did when he was young and our parentsgot a nice lawyer in voice for that (fucked up laws, I know, I know).
Personally I want them to learn about ransomware! If that cost me a PC... My fault.
I have to make this nitpick:
"you" are the one keeping you on windows. You decide that those features are more important than any disadvantages.
Which I think is absolutely OK - that's your choice. Many many people took this choice for a myriad of reasons and are the sum of "windows majority" - and no "I would change if" will perpetuate either feature development on Linux programs nor pressure on Microsoft.
A Dockerfile itself is the instruction set. There is a certain minimum requirement expected from a server admin that differs from end-user requirements.
The ease of docker obfuscates that quite a bit but if you want to go full bare metal (or full AWS or GCS, etc etc) then you need to manage the full admin part as well - including custom deployments.
No worries I phrased that quite weird I think.
A NAS is only more power efficient if the additional power of a full server is not used. If for some reason the server is still needed than the NAS will be additional power consumption and not save anything.
(for example I run some quite RAM and compute heavy things on my server which no stock NAS could handle I think).
The first link goes into amazing detail on that. In short: all your information concerning location as well as current IP and some other metadata gets send to a basically unknown company with no transparency on how that data is handled.
I highly recommend reading the first, linked post though!