And check for each music service their offered music. I’ve checked out tidal actually today with one of those export playlist tools and about 10% of my (honestly: niche) music wasn’t available.

No one forces unattended updates. And containerd is already living in the userspace.

If every dev would live on a kernel level stability approach we’d will not have a containerd release at all.

Seems like a historic artefact to me as well. And one of their mentioned points was “no sync via http” which even for 2006 makes me… hesitant.

And their history section ends in 2007, couldn’t find a feature comparison in their quick start guide.

One thing that was only mentioned briefly by someone else is the physical button turning on the computer.

Similar to the paperclip test figure out where the power button goes into the mainboardw and bridge that with a short cable. Is possible that by moving the case the old button lost a cable.

This is just one more thing to test though, it’s really trial and error as you know :)

From what I understand: CasaOS is simply an abstraction layer and takes away a lot of the manual work.

I agree with you that this shows down learning quite a bit.

I see three ways forward for you:

a) switch to a Linux base system, Debian, arch, nixos, whatever resonates and set up everything from scratch. High learning curve but no more hidden things.

b) same as a but as a separate setup. This is what I would recommend if you have the time and cash. Replicate what’s already working and compare.

c) figure out how to do things manually within the CasaOS framework. Can’t help you there though :)

If that’s your intend than it might be better to pick individual arch wiki pages or improve the entry documentation. Many people refer to there from all distro because of its volume.

A “how to read tech documentation” could add value for this target group.

User perspective:

If you want something big I’d pitch nixos. As in the core distribution. It’s a documentation nightmare and as a user I had to go over options search and then trying to figure out what they mean more often than I found a comprehensive documentation.

That would be half writing and half coordinating writers though I suspect.

Another great project with mixed quality documentation is openhab. It fits the bill of more backend heavy side and the devs are very open in my experience. I see it actually as superior in its core concepts to the way more popular home assistant in every aspect except documentation!

That said: thanks for putting the effort in! ♥

Ah that would make sense, thanks!

I haven’t found (while cross reading ) details about why the “highly improved” didn’t make it to upstream openwrt?

The screenshot had has the criteria included though. Relevant part: either be for children or for everyone.

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!

Deine Krankenkasse wird sagen “Nein, die Leistung wurde nicht erbracht” und die Praxis dann: ok, hier ist die privat Rechnung.

Wenn du letzteres lieber möchtest sprich die Praxis einfach drauf an, dann kriegst du die Rechnung statt der Unterschrift.

Die anderen beiden haben schon den Kontext erklärt,deshalb noch: Nein, das ist keine übliche Redewendung.

Habe das in mehreren Jahrzehnten Arbeit und mehreren Arbeitsstellen noch nie vorher gehört.

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.

OK now I have to escape to really smart assery and assume that’s what I meant the whole time ;)

Edit code 2 describes something that went wrong - but that something telling you that it went wrong was the tar binary which therefor most have been valid to evaluate that!

Under no circumstances did I assume that the hint towards help itself would’ve been an exit code 0, no sir!

To be honest: if I’d designed that bomb it would’ve exploded in my face for trying to be too clever.

tar

Done. That’s a valid command, no error code, nothing. KISS!

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

That would replace the computer with the NAS though and is not true for a server that you’d want to extend, right?