Better software availability/support than BSDs. Refuse to use proprietary software. Plus, there’s a lot of software I use that isn’t available on Windows or macOS. I’ve tried to dual boot Windows for gaming before and I just couldn’t install most of my usual software on Windows.

preparation for systemd compatibility

To be clear, they’re not switching to systemd; they’re just reportedly (I can’t find primary sources on this, only secondary) working on compatibility with programs that expect systemd to be there.

Same. It removes the ability to have plausible deniability of “oh I just forgot to tag it”—no, if you tagged it “non-AI” and it was actually vibe-coded, you clearly deliberately and consciously lied.

I’m just confused as some comments seem to suggest it’s not possible. There are already idle daemons like swayidle, so you just need to have an idle daemon execute a program that plays an animation and exits when it receives any input? I don’t know of any such programs, but I don’t see how it’d be impossible.

There’s screen lockers. Is there a reason why programs like swaylock couldn’t play an animation instead of showing a static image? Am I missing a reason why it’s structurally impossible?

I’ve never seen it on the official web app. I suspect that, if they existed, I would’ve seen them used by now.

But mandating [NOT AI] means that people have to go out of their way to declare their work is AI-free. It requires active lying rather than lying by omission—I think there are a non-zero number of people who would be inclined to omit an AI tag but would not want to go as far as explicitly lying about their work being AI-free.

I would support those tags. Does Lemmy support some equivalent of post flairs that can be filtered?

if I aggressively block each offender in my logs permanently, then the next person assigned this IP who may be a legitimate user will be unable to access my site.

temp bans exist for this reason. You can use something like fail2ban for it, or that may be overkill for your purposes, but any mechanism that blocks the IP address for a short amount of time will work. My f2b blocks spammers’ IP addresses for a day, and I don’t see repeat bans which means the spammers aren’t coming back on the same IP address, so the short ban works to stop a given spam attack.

I also used to use the same thing. Been a long time since I’ve had to remote access someone else’s PC for troubleshooting but I think I also used TeamViewer back in the day (which I assume might not work as well on Linux anymore now that Wayland is the norm?). Perhaps you could write a quick script to get your public ip address by curling some web service that tells you your public ip address, add a desktop shortcut to that script, and over the phone tell the person to double click that desktop shortcut and read out the number they see. It’d still trip up the most tech illiterate but hopefully if they’re at the “can follow clear and basic instructions” level they can manage that. And possibly there are still dyndns clients that do that; I’ve just not messed with any of that for a long time, but you can set that up on their PC if that stuff is still around.

Whichever distro you choose, you could set up SSH access for yourself to do things for them (apart from fixing most networking issues if they can’t connect to the internet ofc).

I agree about the risks in terms of the way some sources present the AUR as just extra packages. But I don’t think you can object to the AUR more than any other place on the internet where anyone can upload software; unfortunately, the onus is going to be on the user to verify what they install. The AUR is moderated by volunteers and it wouldn’t be fair to expect them to vet all of the high volume of commits to the AUR. Possibly they could vet new maintainers or new packages or newly adopted packages, but nothing would stop someone from initially uploading a genuine package and then replacing it with something malicious. Or they could require identity verification to be an AUR maintainer but then far fewer genuine packages would be on there because people don’t want to give their real identity to contribute (I maintain some AUR packages, and would stop if required to verify my IRL identity).

I can totally understand if the AUR is not for you; it’s more time-consuming as you have to read PKGBUILDs (I always do). But that doesn’t make it bad that it exists at all. I think there should be more warnings about it for new users, and possibly some more moderation, though like I said above there’s no perfect moderation solution that would simultaneously forgo users’ responsibility to check and keep the AUR as large as it is today. Ultimately the option should still exist for users who want it. If it didn’t exist, I’d have to hand-package every program that’s not in the official repos, and that’s even more time-consuming than pulling and reading through a PKGBUILD that someone else already wrote and shared.

It’s just a repository of user-contributed packages. It’s no different malware-ability-wise to, say, GitHub. If you are running code you found from a stranger on the internet then you are liable for it, and you need to do your due diligence in checking that you are not running malware. It is a good thing that the AUR exists because it means Arch user packages are all in one centralised repository instead of scattered across GitHub, Sourceforge, Codeberg, Pastebin, forums, whatever. If you are just installing random AUR packages then that’s on you. It’s basic internet safety to not automatically trust random scripts you find on the internet.

What an annoyingly uninformative title. Better title: a lot more compromised AUR packages have been found since our last update.

“A lot worse” is intentionally vague to get people to click.

I mean the ELI5 for the uninitiated is that X11 is older, and Wayland was made as the successor to X11. It aims to address issues that a lot of people had with X11. X11 is not in active development whereas Wayland is, and for support for modern tech, it’ll be added to Wayland but not X11. These days I’d advise to go with Wayland unless you either have hardware that doesn’t place nicely with it or you have a specific use-case for X11, i.e. Wayland unless you have a reason not to. Although most “beginner” distros choose for you without prompting you to pick, in which case go with the default (it’s probably Wayland anyway).

If you mean to explain the debate, basically some people have particular things they want to do, or they want to do something a certain way, and it’s not supported by Wayland, usually by design due to things like security concerns or philosophical differences with X11. X11 will continue to work for a long time but it’s not getting new features, so if these issues are a concern with you, you could stick to X11 for the foreseeable future.

The average user is not supposed to notice a difference (apart from maybe QoL differences like performance, screen tearing, etc)—that’s the goal of both projects. It should just display your desktop.

Maybe block on your router and save your router password such that you need to jump through several hoops to unlock it, eg password saved in one password manager DB whose master password is in another DB whose password is in another DB, etc. If you have to unlock like 10 password databases to get into your router, you’ll probably give up on whatever bad habit you were trying to do as it’s too much effort.

If you want to learn more then do LFS. I don’t think Gentoo teaches you much more than a manual Arch install. But very few daily drive LFS. It’s hardly practical. Gentoo is daily drivable but if you don’t care about compiling all your own packages then I don’t think it’s for you.

I’d say just do LFS on an old laptop or a VM.

Yay

I only use flatpak for one Python program because it has a lot of runtime dependencies I don’t want to bother with. I generally wouldn’t use flatpak.

If you haven’t already, I recommend Watchtower (nickfedor fork—the original is unmaintained) which automatically pulls updates to Docker containers and restarts them. Make sure to track latest, although for security updates, these should be backported to any supported versions so it’s fine to track an older supported version too.

Notesnook notebook with whatever info I need to be able to administrate the system. e.g. what different ports are used for and why the firewall policies are what they are, sometimes write-ups after a troubleshooting session, etc.

The Notesnook instance is self-hosted too, but if the server goes down, the notebook will still be available locally.