If you’re interested in (co-)moderating any of the communities created by me, you’re welcome to message me.

I also have the account @Novocirab@jlai.lu. Furthermore, I own the account @daswetter@feddit.org, which I hope to make a small bot out of in the future.

  • 7 Posts
  • 55 Comments
Joined 10 months ago
cake
Cake day: February 27th, 2025

help-circle

  • Here’s why you’re getting enshittified: we deliberately decided to stop enforcing competition laws. As a result, companies formed monopolies and cartels. This means that they don’t have to worry about losing your business or labor to a competitor, because they don’t compete. It also means that they can handily capture their regulators, because they can easily agree on a set of policy priorities and use the billions they’ve amassed by not competing to capture their regulators. They can hold a whip hand over their formerly powerful tech workers, mass-firing them and terrorizing them out of any Tron-inspired conceits about “fighting for the user.” Finally, they can use IP law to shut down anyone who makes technology that disenshittifies their offerings.

    You can take care to avoid enshittification, you can even make a fetish out of it, but without addressing these systemic failings, your individual actions will only get you so far. Sure, use privacy-enhancing tools like Signal to communicate with other people, but if the only way to get your kid to their little league game is to join the carpool group on Facebook, you’re going to hemorrhage data about everything you do to Meta.

    https://pluralistic.net/2025/07/31/unsatisfying-answers/#systemic-problems






  • Yeah, unless one happens to have one of the beefier Raspi 4 or Raspi 5 variants (which, of course, cost way too much money if their sole purpose is to be a home server). To give specific recommendation for cost-effective beefier home server hardware: Used Thin Clients. For example, Dell T530 Wyse (or T520, or T540, or the 6x0 series).









  • A few months ago I wrote out some recommendations around the same theme here. Extracts:

    A good start is to install tldr. You use it like man, but it gives you shorter explanations – or rather, a short list of illustrative examples.

    Going further, check out Fish instead of Bash. I haven’t use Fish yet, but it’s said to be much better for learning Linux commands as a beginner. Later on, you may switch to Zsh. In any case, hitting Tab once or twice will often give you a list of possible completions to the command you are typing.

    Also, I hugely recommend reading at least one book about Linux. I’m now almost through with the O’Reilly book “Classic Shell Scripting” by Robbins and Beebe (ISBN 9780596005955). Despite the fact that it’s 20 years old, it helped me hugely – primarily with the shell and its commands, but also with understanding things like file structure.

    It presupposes some familiarity with Unix-like systems and with the shell, so if one’s just starting out, the book “Learning the Unix Operating System” may be better.



  • It’s still workable for sure.

    Above all, memorize one thing: When you update, and then reboot, keep an eye on the computer during reboot, especially during the early stages. That’s because every month or so, when the drivers have gotten updated, you will be presented with a (often blue) screen about MOK Enrolment, i.e. you need your UEFI that the new drivers are trustworthy. If you miss this screen, you’ll boot into a black screen or so without anything telling you what the error is, and to fix it you’ll have to enroll those keys manually – this is not prohibitively difficult, but annoying. (That’s if you have UEFI secure boot enabled. If you have it disabled, there is practically no pain at all, ever. You lose a bit of security though. Personally I have it disabled.)