• 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: December 25th, 2023

help-circle
  • 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 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.






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



  • 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! ♥









  • (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.