Niccolo Ve did a pretty comprehensive summary of all his problems recently: https://inv.tux.pizza/watch?v=mhqeuO9RKKk

He’s been on a right-wing, transphobic, anti-woke downward spiral for years now.

of course not!

Handbrake will probably still work if you compile it from source, but it seems like upstream isn’t paying much attention to libdvdcss support.

The version in Debian’s repo still works for me, anyway.

Yeah, it’s fake, and as other commenters have pointed out, it’s also inaccurate to how the GPLv2 works. It was not meant to convince anyone.

I’ve never used these, but I’ve come across them while scrolling through F-Droid and they seem to fit this use case:

Kotatsu
Kinoko

I came across a bunch of those recently, which is how I came up with the idea for this, as a parody :)

Internet horror is disappointingly un-creative. I have no idea why the weakest works (sonic.exe, anti-piracy, kill screens) always end up becoming huge trends, or why so few people try to put a significant twist on said trends.

Tons of companies are shipping Linux without giving users access to the source code, it’s just that only one has the term “Tivoization” named after it.

I’ll probably use Codeberg or another Forgejo server for my next programming project, if/when I have one that is far enough along to publish (motivating myself to get that far is a tall task). Until then, everything I’d consider contributing to is either on GitHub, or is self-hosting some other software, so I don’t have a reason to create an account yet.

https://github.com/TeamNewPipe/NewPipe/issues/11139

I’ve switched to FreeTube for now, it still works using the Invidious API. This is happening because YouTube is testing forced login to watch videos or use the API. There is a workaround it seems, but we’ll have to wait for all the major clients to roll it out.

The website claims that sponsors have no direct influence on the project (“board seats are not for sale”). The reality is that no project of sufficient scale to fully implement web standards can survive without a significant amount of funding.

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.

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.

For me, the outdated packages in stable have actually gotten better over time, as DEs get closer to a place where I don’t need any major updates to enjoy using them, Flatpaks become more readily available, and on a subjective level, I get less and less invested in current Linux news. Before Debian became my “forever distro”, I’d hopped to it a few times, and often found myself wishing for a newer piece of software that wasn’t in backports or flathub, or simply being bored with how stable it is, but that’s been happening less and less. And I feel like Debian 12 in particular left me with software that I wouldn’t mind being stuck with for two years.

I’ve gotten warnings to upgrade my browser with Debian’s Firefox ESR, but they never affected a website’s usability in a way that a newer version would fix, and they do provide security updates and new ESR series when they come out; even if you must have the newest Firefox, you can use the Flatpak.

Additionally, I’m currently on testing in order to get better support for my GPU, and each time I’ve tried to use it, it’s worked for me for a longer time than the last as I get better at resolving or avoiding broken packages. If you do experience issues like the one you described, and can replicate them, and no one else has already reported them, you should report them to Debian’s bug tracker. The whole point of Testing is to find and squash all the critical bugs before the next stable releases.

I always keep close track of these contests, it’s fun to take a look at all the different concepts. Though IIRC only Juliette Taka (who designed the themes for 8, 9, and 11) even submitted a theme last time. She’s great, and Emerald is great, but I hope this post gets someone even better involved with the artwork.

I was quite satisfied with Debian Stable for a few years on at least two different laptops, and felt I had found my “forever distro”, until I got a Framework laptop whose AMD graphics were quite buggy on it. In order to get rid of all the issues, I had to upgrade to Testing and install a mainline Liquorix kernel (and along the way, I briefly made a Frankendebian and fiddled with kernel parameters). While my years of experience with Debian and derivatives has prevented me from breaking anything, I do wish I didn’t have to use all of this beta-quality software just to prevent games from freezing and crashing constantly, just because I bought “new” (about a year old) hardware.

I still want to keep Debian, because I’ve found nothing else that works quite as elegantly or stably, but I’m hoping to find ways to get the performance I need without Liquorix, and if something forces me to reinstall between now and the time Debian Trixie becomes stable, I’ll probably give Fedora or KDE Neon another try.

Debian can still work, but you’d have better chances with legacy LXDE, or starting with no DE and installing IceWM.

Q4OS Trinity, antiX, and Damn Small Linux are all Debian derivatives known for being able to run on very old systems, and they’re among the most lightweight distros I know that are still functional for most purposes.

Not sure why, but a lot of other distros did something just like this in the past (see the comments about WUBI) and no longer do. Q4OS still has a .exe installer though.

1. Create a source control repository containing all your code, and publish it to an online code forge. GitHub’s docs might help with this: https://docs.github.com/en/get-started/start-your-journey
2. Choose an open-source license and add it to the repository as a LICENSE file. If you want to require any projects that build upon yours to be open-source too, the GNU GPL is a good choice. If you want to allow proprietary programs to include your library without releasing any source code other than that which is directly based on yours, the GNU LGPL is good for that. If you want to allow people to do whatever they want, even use all your code as the basis of a proprietary program without credit, the Unlicense is a good choice. There are a lot of licenses with different degrees of “copyleft” and attribution requirements in between. Technically publishing with a license file is all you need to do, but there are more things you should do.
3. Create a README text file describing what your program does, and instructing users on how to compile and run it. Consider including more detailed documentation on how to use it, as well.
4. Clean up your code and file layout so that it’s as easy as is feasible for other programmers to understand.
5. Promote your project to whoever you think might find it useful!

Unfortunately, the state of Android music players is not great. Currently I have two FOSS music players installed: Metro Music Player (the F-Droid version of Retro Music Player) and mucke. mucke has a ton of really cool features that improve the shuffle experience but it’s actually worse than most apps at pulling album art. Retro/Metro has beautiful UI, and has pretty good features for customization, but lacks the cool features mucke has and is less stable. Both have more than one annoying bug, but it took me a while to find music players that had this few dealbreakers.