chrisp

@chrisp@cyberplace.social

• ⁨Comment⁩ on ⁨Self hosting Signal server⁩ ⁨⁨2⁩ ⁨days⁩ ago⁩:

  @UnfortunateShort @KarnaSubarna And you'll want to audit the client code of the fork, including dependencies and make sure it is keeping up to date with official development for security patches. And Signal may try to break the interoperability at some point in the future.

• ⁨Comment⁩ on ⁨Self hosting Signal server⁩ ⁨⁨2⁩ ⁨days⁩ ago⁩:

  @UnfortunateShort @KarnaSubarna I think you are right about the official client, they really want to own the service so you can only connect to their decentralized service via their centralized servers 🙄 I haven't done it, but I think you can run your own client, either modifying and building it yourself, or surely one of the existing forks can connect to arbitrary servers? But anyone who wants to use your server will have to also use one of the forks.

• ⁨Comment⁩ on ⁨Is this the end of Bootloader Unlocking in the EU?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  @balder1991 @Lembot_0004 "Working on electronics in your parents' garage? What are you, some kind of terrorist?!?"

• ⁨Comment⁩ on ⁨Ansible sounds interesting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  @beerclue Exactly. You can take wiki bash instructions on how a system was set up and translate it to ansible, or back again. The ansible modules are python, but theoretically you could make a bash implementation that just calls dnf/systemctl/etc. directly, like a sys admin would have done.