If on he other hand you want a transition that’s really painful and slow but sooo rewarding (highly subjective, of course) you can look into nushell. They just said “screw this 50 years of conceptual baggage and let’s do it data centric and proper”.

I still am at perhaps 10% the speed of my zsh setup but the concepts are so intriguing I’m sticking to it. At least I try to …

The first part is a technical question and the second part a definition one.

For the how to: the most common approach is to simply blacklist their IPs on a provider basis. This leads to no provider that obeys your blacklists to allow their users traffic to that target. Usually all providers in a nation obey that nations law (I assume, I only know that for my own :D)

For the censorship: I don’t like that word because it’s implications fan be used against any and all laws. A shitload of content is made inaccessible because it breaks laws from active coordination of attacks to human trafficking. All of this can be described as censorship.

Forthe UK law it’s… I’m not British and to me it appears to be a vague tool to silence and control all types of content under the guise of protecting children. Not with the intention to protect or prevent something but with the intent to control. I would fully understand and emphasize with using the word censorship in this context.

You won’t get the AI stuff through. I’m working on a machine like you described and drilled a hole in it to provide power to a 3070 as the power supply wasn’t beefy enough (and server power supplies are too expensive compared to a hole).

This is the first generation where I can play around with local LLMs from what I can tell - even used the hardware for that is way more expensive :(

This is a proposal. Why does the article write as if it’s a fact?

You got a lot of relevant answers so I want to point out something else:

You’re hosting your own services. By yourself. Fuck everyone with a broom who tries to gatekeep that. And I don’t mean wooden side first.

Seriously, your question is on point here from my perspective and as long as it has a connection to running services by your own I personally would love more diversity in hosting solutions.

Personally, I’d love to see people share more about their provider agnostic opentofu deployment or someone who went all in on AWS lambdas for weird stuff.

Hey,

I’d be very grateful if you could share your approach den if it’s only to compare (I went with a “be assertive and clear, skip all overhead” system prompt.

This is not only interesting for chatgpt but understanding how people solve these issues comes in handy when switching to local variants as well!

Thanks in advance

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.