• 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: February 19th, 2024

help-circle






  • I’m not familiar with what’s been said or done regarding bots, but I’d be surprised if they were planning to shutdown the self-hosting part? But I can see how they might shutdown the free cloud auth aspect.

    As RD consists of the server/client software and the authentication software, the latter is also made available online to all with no reliability promises. But there’s nothing stopping people from hosting both parts locally, and is how I implemented it. No traffic to third parties, etc.

    Can’t advise on domain-based setup, as I’ve not tried it, but depending on how you’re planning to use it, there may be no need for a domain. I only used mine locally (or via WireGuard when outside), with hbbr and hbbs hosted in Docker on my NAS, and it worked fine with my mobile devices and PCs.




  • I followed a science starter pack, thinking it’d be, well, wall-to-wall science with a bit of random everyday stuff mixed in. Right?

    Nope. Turns out, thanks to American current affairs, almost all of its members post political content almost all of the time. Close to the last thing I want to see on social media. (I don’t blame them, as they’re being hit hard by it all.)

    To make it worse, most Bluesky users don’t “do” hashtags or content warnings (unless it’s promoting something - remember to like and subscribe!), so it’s incredibly difficult to filter out the clickbait and rage-sharing. 😟



  • After too many wild rides with Watchtower auto-nuking services, thanks to breaking changes (migrations, DB updates, deployment changes, etc), I switched to What’s Up Docker and pin the version for all of my containers.

    WUD lets me know when something has an update, so I periodically go through their release notes and do the update(s) manually. Usually as simple as read the notes, changes version in compose, down (or pull), then “up -d”. But this approach has saved my bacon multiple times.

    I’ve seen there are other solutions - of varying degrees of promises vs delivery - but most of my stuff is long term and stable. My approach maintains all that.




  • My recommendation is Debian for a server (real or virtual), or Proxmox. The former is perfectly reasonable and excellent experience; the latter is more flexible and more complex.

    Debian is the parent distro of numerous Linux flavours (including *buntu, which aren’t suitable as a server OS, IMHO), so administration and services are all common (apt, etc). No need to learn dnf, pacman/yay, etc.

    It’s still my preferred server OS, despite other options and being experienced.

    Though I do also have a NUC running Proxmox (for VMs and LXCs), and both a NAS and RasPi running Docker. 🤷‍♂️ My Debian server is a VM inside one of them.


  • While user consent (default on vs default off, or any choice at all) is a different-but-related topic, Mozilla bake it all in, enable it all by default, and make it difficult to disable. (Settings would be “super easy” and would show it was intended as a permanent choice.)

    These aren’t actions and design decisions indicative of having the best interests of users in mind. Especially given how closed the mobile client already is.

    It seems to be designed in a way that leaves Mozilla the option of removing the ability to disable it, presumably if it becomes profitable enough and/or they think they can get away with it.

    But for now on this point they get a pass from me on the desktop version in a personal environment where the user has the most control.


  • Because the Argument of Excluded Middle (aka false dichotomy) logical fallacy is king now. With no middle ground for compromise, if you’re not 100% for a position then you have to be 100% against that position. It’s the rules.

    So, with that batshittery in mind, anything that allows you to optionally use something that people (justifiably) detest is, of course, the literal devil.

    I blame brain worms.




  • It’s true that people on the internet can be dicks. Even more so technical people (and that’s not limited to online: those online dicks are usually IRL dicks when taking technical stuff). But that’s a hurdle, not a barrier.

    There’s little anyone here can do to help OP, as they (if I understand it correctly) have already irreparably nuked their hardware. The current problem is significantly different and harder than the original problem. Asking randos on this community is unlikely to yield results. Hence the focus on variations of “Now… what did we learn? 🤨”

    I’m not trying to help, as I’m not familiar enough with SAS nor the current problem. The same is likely true of others here.