ipacialsection

Where'd you get the OneShot Firefox icon?

This article seems to assume that advertisers don't want our identifying information, and are clamoring for an alternative to tracking that lets them measure ad performance anonymously, which is just not true. Being able to uniquely identify users and target them is a feature, and getting more data points from the browser just helps add to their profiles.

I'm not averse to trying new foods, but I have strong aversions to certain foods that I have tried. If I have a bad experience with one food, I will not be willing to try it again for a very long time, possibly ever. And if I have a good experience with one food, and it is easily available to me, it will remain in regular rotation for a very long time.

These are the mixes of the Federation DJ Enterprise. His five-hour mission: to spin strange new records, to seek out new sounds and new labels, to boldly crate-dig where no DJ has dug before. (disco Alexander Courage theme plays)

I'm against a megathread. That would be too busy and I think there will be more than enough to discuss about each episode.

For entirely selfish reasons, I'd like individual discussion threads for each episode that come out one or two a day, since that's the pace I expect to be watching it (optimistically).

Though, I think the best option for everyone might be five-episode blocks. That would allow both bingewatchers and slower viewers to enjoy the conversation without spamming the feed, and will match up well enough with the "parts" it would have been split into if it aired on Nickelodeon that both broad and individual episode discussions will make sense.

Yeah, 50% (ram / 2) seems about right.

The major tradeoff with zRAM is that programs are much more likely to crash due to running out of memory, but will run faster when memory is running low and freezes are less likely. You can think of it as offloading the pressure that traditional swap puts onto your disk, onto the (much faster) CPU. There will be an impact on CPU usage, but not enough to cause noticeable slowdown; in my experience running Linux, the CPU is almost never the reason something is slow, and is only going to be under significant pressure if you're running a 3D game in software rendering, compiling a large program, or another complex CPU-bound task.

I wouldn't recommend making the switch unless you often encounter system freezes or slowness while running tasks that use a lot of RAM (like web browsing on certain sites, or gaming), but it will improve things in that case.

You can install an antivirus, but you really don't need to. Malware for Linux is rare, and malware that targets desktop Linux users is extremely rare (to the point that it's a newsworthy story every time it does appear). Most distros have ClamAV and the frontend ClamTk in their repos, but it's primarily used to scan servers for Windows malware before it reaches its intended target. Some Windows malware can still be harmful if run with Wine/Proton, but unless you're downloading and running a lot of Windows software from unofficial sources (which you shouldn't have any reason to) that won't be a risk.

I'm using an AMD Ryzen iGPU on Wayland. I switched to Testing because the support already existed, but the kernel and mesa versions in stable were buggy for my particular GPU and I didn't want to make a FrankenDebian.

It's not systemd's fault, though systemd most often implements offline updates. The arguments for and against offline updates have nothing to do with systemd.

A lot of Linux distros, and graphical package managers like Discover and GNOME Software, are moving in that direction, under the argument that updating while online can cause disruptions to running software, in the worst case including the package manager itself (which can brick the system if it occurs in the middle of a critical update), and updates can't be applied until the affected program (or the system, in case of critical components like the kernel) restarts anyway. Fedora Magazine explains the reasoning here: https://fedoramagazine.org/offline-updates-and-fedora-35/

In my personal experience though, I have never had an issue enabling automatic online updates on Debian Stable, and have had computers stay online for several months without any noticeable issues beyond Firefox restarting, so the risk is there but it's pretty minor.

Depends on your desktop environment. Look for an "autostart" or "startup applications" setting. If you're on KDE, this could also be caused by "Restore previous session" under Settings -> Startup and Shutdown -> Desktop Session.

I personally don't use Arch, but I think the reason so many people find it stable in practice is because they know their system well. When something breaks or needs to be changed, they know which configuration file to edit, which package to {un,re,}install, what to look for in the AUR, etc., and they can usually avoid those things in the first place, because they went through a fairly hands-on install process, not to mention having the best Linux wiki in existence at their disposal.

On top of that, I think a lot of derivatives of Debian, including Ubuntu and all its derivatives, severely undermine their stability by providing custom configurations for or changes to software that are rarely documented and completely transparent to the user... until they break and leave no indication of how to fix them. Which is one reason why I ended up using base Debian.