Yeah bikes are less dangerous, not as fast, more control, better view, more maneuverable.
What about bards that woo young maiden?
Those things arent very loud lol
EU too. The rules seem pretty good actually and I think they might actually improve safety. On my bike tbh I use noise to check if there are cars all the time. Never had many issues tho, but most cars are not electric
Name 3 other constant sound sources. Construction does not count.
Wait, that is an artificially created sound??
I like the idea but why do they have to make these cars look so weird all the time, instead of literally just the same?
It is kinda matte, lower details, no ornaments etc.
Also with the bumper, window frames, lights and rims it looks like a damn toy. Ugly af
Favourite, for beginners or for people who wanna learn?
That would be nixos, fedora kinoite (ublue main image) or anything you build up yourself a bit like debian or arch maybe
How so?

At least it is the only software project so not technically a dupe
It is not easy to recommend a distro, even though many people are quick to recommend one.
This is because they may not think of all the things that make up a Linux experience. This is my attempt to paint a bigger picture.
Intro
expand
ℹ️ A Linux Distribution (short Distro) is a bundle of the Linux kernel together with many different components that build an operating system. These components include a package manager and a desktop environment. The package manager is important to guarantee that your system will work and be secure in many years. The desktop environment (short DE) is the interface you interact with daily. They are very different, and most DE's work on most distros.
There are many factors, and balancing between them is the only way to get the right distro for you.
After having tried a lot of them, these are the main factors I would think of, when looking for the right one for you.
🌌 Do not hesitate to try Linux! Most Distributions can be tested on a USB stick or in a virtual machine without changing your system. Depending on the amount of switching and work you want to risk in the future, your decision is more or less important. Many people will try a bunch of different distros and get to something they like later on. But if you need to decide for other people or a company, you want to avoid switching and issues.
1. Desktop Environment
expand
All common distributions will package and/or include most software that you need.
But the desktop environments that you use to interact with the PC are less or more supported, some distros may not offer some of them at all.
Generally, KDE Plasma and GNOME are the most complete environments, modern, with the biggest communities, quickest maintenance, most features etc.
Here is how GNOME looks like:

And here is KDE Plasma:

Many distros prefer an environment. GNOME had the reputation of being more stable than KDE Plasma (this improved but GNOME is still significantly simpler). Due to this reason, many (especially enterprise focused) distros chose GNOME as "main variant"
- Ubuntu (moderately customized)
- Fedora (now equally with KDE Plasma)
- RedHat Enterprise Linux, CentOS Stream, AlmaLinux
- VanillaOS, ZorinOS (heavily customized)
Many distros have KDE Plasma as main desktop too
- Manjaro (Arch based)
- OpenSUSE
- TuxedoOS (Debian based)
- SteamOS (Arch based)
- Bazzite, Nobara (Fedora based)
Other distros dont prefer a desktop environment
- Arch Linux
- NixOS
- Debian
- Gentoo
KDE and GNOME are generally well supported on all bigger distros. Other desktops might differ. For example, Fedora has a Cinnamon variant, but Linux Mint likely has better integration, presets etc. Lubuntu has a way better looking LXQt desktop, while Fedora ships a working Wayland session. XFCE exists on many distros, but Xubuntu, Linux Mint XFCE or KaliLinux will look very different.
So as a beginner, take GNOME or KDE, they are both nice but different.
2. Release cadence
expand
This is a big difference. On Windows every app updates on it's own (which is pretty horrible), and the desktop and OS are kinda stable (more so before Win11), barely releasing any changes.
On Linux, traditionally you install your software from the same repositories as your main system (including kernel, core tools and desktop environment).
Though, with things like Flatpak it is possible to get all the recent apps, independently from your system).
Quick Updates
If you want up-to-date software, you often need to choose a distro with fast or rolling releases. These typically have a shorter support span, so version upgrades every 6 months or year are common.
Downsides are potentially more bugs, as the software you use is newer and less tested. But if bugs are fixed, you get those fixes faster too! You get way quicker features and many security updates not arriving in "stable/stale" distros.
Examples:
- Arch
- NixOS unstable
- OpenSUSE Tumbleweed
- Debian testing
Semi-fast:
- Ubuntu
- Fedora
- OpenSUSE Slowroll
Slow, "Stable" Updates
If you prefer stability and reliable software (so that you dont need to update often, or change scripts or tools if software changes features), you should use something with long support and slow upgrades.
Note that stability is not natural to most software. Most is "released when it is ready".
- Only very few projects release on tight schedules (like GNOME, Firefox, Thunderbird).
- Way fewer developers "backport" all security fixes to old versions. This means they apply only the security changes to older versions, while leaving out feature changes (which could break compatibility).
- The issue is that most developers dont have the time to adapt to adapt their software to all the different release cycles of different distributions
- So you have potentially broken or insecure software until there is a distro upgrade
Examples:
- Debian stable
- Ubuntu LTS
- OpenSUSE Leap
- RHEL, AlmaLinux, CentOS Stream
3. Project Size And Structure
expand
Size
- Bigger projects (like Ubuntu, Debian, Fedora, Arch, OpenSUSE, Gentoo, NixOS) have the most software support. This becomes less relevant through technologies like Flatpak (a unified packaging format for all distros)
- Smaller projects (while nearly always being based on bigger ones) will often add more quality-of-life changes, customizations and features. Take Nobara, CachyOS, Garuda, Pop!_OS or Bazzite, which contain many improvements for gaming (more or less at the cost of stability).
Bigger projects are often more conservative, with a focus on stability and not changing software a lot. Depending on the distribution, you may also be able to do many changes yourself, while using a bigger one as the base.
Structure
Most Linux Distros come from a "community". This is fundamentally different from Windows, MacOS, ChromeOS or Android, which are sold products without much or any community involvement.
The projects differ in how you interact with developers, contributors and how people in the community help each other.
The "communty" is mostly never equally distributed, as most users will not contribute to the project.
Often the developers communicate on Matrix, IRC or even mailing lists, users might interact with them through bug reports.
Forums are mostly used for users to help each other, with mostly little interaction with developers due to their time being scarce.
Many free "community" distros are backed by companies, as making a distro costs a lot of money and benefits from a stable base of employed people
- RedHat does their stable distro RHEL.
- The "upstream" (the newer stuff that is not as tested and arrives later in RHEL) is CentOS Stream, which technically is already a community project, together with Oracle, AlmaLinux and RockyLinux contributors.
- The upstream of that is Fedora, which is a known, free and up-to-date "community" distro. But also Fedora is built and maintained in part by RedHat employees, so this is a mix.
Other examples
- Canonical - Ubuntu
- SUSE - OpenSUSE, SUSE enterprise Linux
- System76 - Pop!_OS
- ZorinOS, EndlessOS: payment models
- TuxedoOS - Tuxedo
- SteamOS - Valve
Many distributions are entirely community based, like Debian, Arch or Gentoo.
Some have slight company involvement, like NixOS.
4. Software Modifications and Additions
expand
Distros differ in how the projects modify the software they ship.
Some may focus on fast updates and little modifications, like Fedora, Arch or others.
Others like Ubuntu might add a completely custom theme, font, iconset and other extensions (they do that to the main Ubuntu variant, but Kubuntu, Xubuntu, Lubuntu are also all customized).
Some distros might change software, like Fedora or Debian who only ship free software (software that respects users freedoms).
ℹ️ Example: Debian modified Firefox in the past, to remove antifeatures, which resulted in a ban to use the name. They used "Icecat" instead, but nowadays they ship regular Firefox again.
The Linux Desktop is only somewhat standardized through organizations like Freedesktop.org, who host
- (flatpak](https://flatpak.org/), a technology to ship apps to all distros, while also using an Android-like sandboxing system.
- portals that allow applications to access system components while asking users
- Wayland, a display and input/output technology that all modern desktops and toolkits use
Examples of differences
- Fedora and Ubuntu use different tools for power management.
- Most distros use systemd, a useful system management tool. Some criticise it for being too big and doing too much. Very few distros do not use it, at the cost of missing features and requiring more experienced users.
- Ubuntu uses Snap for their packages, most other distros use Flatpak.
- All distros have their own native packages, but there are a ton of different package formats and rules.
5. Deployment Model
expand
This describes how a distribution is installed and updates.
Installation
Distros are mostly installed the same way: you flash an .iso to a pendrive, run a graphical installer, select between more or less options, and get the thing.
Some may not have a graphical (GUI) installer but a terminal based one.
Many advanced distros like Arch, Gentoo or NixOS direct you to a wiki, where you learn the steps you need to setup the system you want. This is a great learning opportunity, but may require some time.
If you want to install a more complex distro, maybe you find someone to help you with the setup!
Software installs and updates.
Keywords:
- learning curve
- stability over time
Unlike Windows, software shoulf always be done through package managers.
⚠️ Do not go in the browser and get random installers. These might exist, and there are "Appimages" which allow developers to package their software that way. But the install method is insecure!
While it may seem similar to Windows, MacOS or Android, those operating systems include verification checks, antivirus and permission systems that can stop a lot of malware. Linux does not have this, as repositories are the intended way to install things (where those checks exist).
There is a difference how the software is placed and managed on the system. Most distros are "chaotic" and imperative: You write...
sudo apt install libreoffice
...and the package manager searches the repositories, gets the files and places them somewhere.
Over time, "state" builds up. This is the amount of changes on your system compared with how it was at the beginning.
The graph from this master thesis describes this process, called "Divergent".

You enter that command, and the package manager not only installs Libreoffice but also many dependencies.
Convergent
There are many tools that try to tackle the resulting "chaos".
They try to make the setup of your system faster and more reliable.
What happens if your PC breaks down, or you needed to configure your exact setup on 10 different laptops?
The most common tool is Ansible, which is described as "Convergent" on the graph. The system is a chaos, but the more you configure and "fixate" through Ansible, the easier it gets to reproduce.
Image-based
There is a wave of new "immutable" distros, that try to solve this issue:
Oh when you open the app XYZ it crashes? Well, it works on my machine...
They do that by either preventing you to change the core system at all, or always keeping track of the default setup, where your changes are just an overlay on top of it.
This model works for many use cases, as with Flatpak, Homebrew and other ways you can install your softwate pretty normally.
You will not need to worry about the base system not being able to upgrade, or break in other ways.
Deterministic
Systems like NixOS are deterministic instead of imperative.
To install software, you write down what you want into a file, and the management tool reads it, checks it for errors and builds the system that way.
The graph describes this as "congruent". At the beginning your system is very simple. The more you configure, the more complex it gets.
These distros are perfect for more experienced users who want a stable and reproducible system (i.e. when it breaks they know where the error is and how to revert it).
Coming from regular chaotic distros and then an "immutable" distro, this is honestly pretty great.
While the learning curve might be a little bigger, you can easily check what you changed on the system, allowing you to fix breakages insteaf of reinstalling every year.
Everything is configured in a single – or a few – files. You can take these and recreate your system anywhere
If your PC breaks, and you have your data, it takes a few minutes and you have your system back!
You can find a lot of configs on the internet, here is mine, where I try to visualize the different levels of complexity, starting with a very simple system.
Conclusions
expand
Done! So these are the points you need to keep in mind when choosing a distro. Yes it is a lot, but depending on your goal, it might be an important decision.
Do not just go to distrowatch or other random places and install what is hyped the most.
Examples for logical fallacies of "this distro is the best for beginners"
- Ubuntu has a big community, good software support and is easy to install. But personally I had maany issues with it over time and upgrading it. They also have a lot of biased choices and modifications. Their snap store is not what any other distro uses (but they have flatpak support), they theme the desktop and break some functionality, ...
- Fedora also has a big community (and a nice one!), an easy installation and stays with standards more. Their model of "immutable" (i.e. managed) systems is among the best. Meanwhile the traditional variants usinf the dnf package manager are a total mess. I had many extremely complicated and undocumented issues when upgrading and having issues. Also, if you want a congruent, long-time-stable system, it is kinda annoying.
- "Linux Mint is userfriendly" is not completely true. They do good work, but the project is very small compared to it's userbase, they build their own desktop environment that struggles to be up-to-date. They dont use modern design choices like well working automatic upgrades, leading many people to never update their systems. While many users may use it for very simple tasks, it's package based nature doesn't make it very suited for simple "install and forget" installs.
The "most beginner friendly distro" is not always the one that is quickest to install and easiest to use.
There are some points missing which I plan to include
- differentiation between desktop environments
- security
- update behavior
I own an old junky PC that can encode but it is slow and energy intense. Also a laptop that I dont wanna use.
This is a horrible time to buy hardware with soldered memory, but used Mac Minis are available.
I am looking for raw and efficient CPU power because from my experience GPU acceleration for encoding always sucks (got an Intel Arc with qsv av1 and it is very fast but less efficient and inconsistent)
I want to use ffmpeg with svt-av1 and a few filters for artificial grain generation or noise reduction. With my PC, these filters totally kill performance, from 1,5x speed to 0,1-0,05x speed easily.
Anyone here use a mac mini for software encoding? Even better, with Linux, and with svt-av1?
I wonder what might cause these slowdowns and if unified and crazy fast memory might be able to improve this.
Also, how is memory used here? For my usual ffmpeg encodes I dont need more than 16GB of memory, and that is VERY widely available (used market; shitty low spec hardware is way more frequent).
I would try and get NixOS with Asahi kernel and patches to run there, maybe also just Asahi? Never used Arch, at least it doesnt have version upgrades like Fedora that break.
Maybe run it as a headless encoding server and connect over ssh, access my files from my server and control via my laptop
Intro
Soulseek makes it WAY easier to share files with everyone than Torrenting.
You need an account anyways, so all you need is a VPN that allows you to forward ports, or (if you are a country that doesnt care) open them in your router.
Yes that is a barrier and yes there are many privacy friendly VPNs out there that don't allow port forwarding (mostly not because of filesharing, but because people hosted CSAM and other horrible shit). But still there are very cheap VPNs out there that offer port forwarding (hint: some of which might currently offer big discounts because of their anniversary).
So assume that someone who wants to download from other people is unmotivated, lazy and does not want to spend money. Yes it is a barrier, but come on, it is not big.
Side note: legal issues
Many countries like Poland dont care about downloads and only ban uploads of countries.
This can mean that people there don't even care about using a VPN and simply never share.
Reminder: not sharing is still the default on most filesharing networks!
So by blocking leeching-only users, you will block those.
Copyright companies
It is generally also not a legal problem for copyright companies to download "their" media from filesharing sites.
So by allowing users who do not share to download things, expect that you will get downloads by them. I have had weird users that downloaded every first file of every one of my albums for example.
You will block those, unless they share their "own" content (which would be ironic) or random other content (which would be very illegal).
Block leechers
There is a family of extensions that do this, forked from each other.
I use this one that is simple, kinda up-to-date but has no weird things.
The +proveit variant also adds a sort of captcha system, which resulted in everyone getting banned for me.
Sadly common for all of them is that the in-app documentation is kind of nonexistent, so you need to guess a bit what each option does.
I will refer to the former extension from now on.
You can set a message to write to people who were blocked, and choose to block "suspicious sharing patterns" whatever that is.
You can also set a minimum of files and folders shared. I would say setting 10 files and no folder limit would be a friendly preset.
Missing...
There are a bunch of slsk_xxxxxxxxx users downloading singular files from me and never sharing back.
Those might be using some braindead automated streaming software (hence the automated username and single files).
They appear to share files, but none of them are "enabled". I dont know what that means, but I will try to block all of them.
Anyone know how to auto-block users based on username? This might require a fork of the extension.
There is a barely online HTTP-only website of some guy who makes a software called "FindVUK". No idea how it works and what it does (yet), but the guy maintains huge databases of BluRay decryption keys.
Those keys are needed to decrypt encrypted BluRays. VLC together with libbluray and libaacs can theoretically use those keys to play the content.
It should be possible to use that stack to recreate something akin to MakeMKV with free software.
For now, here is the magnet link to the torrent including website archives and also libaacs (for Windows and MacOS, it is small so why not).
(The website is archived in the torrent. I dont share the link on purpose as it is BARELY online. Needed to download 2 text files at a time, that was the maximum or I got an error 503).
cross-posted from: https://slrpnk.net/post/36195475
I am trying to add a calendar in iCal format to my phone.
Fossify Calendar is nice and fully offline, using DAVx5 as sync adapter.
The link looks like
https://example.com/cal/export/5o2b2j393b21owbd829273b3
In DAVx5 I can only add an account, which does not work for this link. The only direct link to add is a WebDAV filesystem mount
Solved
You need this app for ics links that are unidirectional. Annoying (another app running in the background) but works.
Same with DAVx5, after adding the calendar, go to settings in Fossify Calendar and "add CalDAV calendars".
cross-posted from: https://slrpnk.net/post/36195475
I am trying to add a calendar in iCal format to my phone.
Fossify Calendar is nice and fully offline, using DAVx5 as sync adapter.
The link looks like
https://example.com/cal/export/5o2b2j393b21owbd829273b3
In DAVx5 I can only add an account, which does not work for this link. The only direct link to add is a WebDAV filesystem mount
cross-posted from: https://slrpnk.net/post/36077652
I succeeded in using Haveno (Called RetoSwap when used on the mainnet). It was quite confusing so I will document the TLDR here and give a guide about the use on Linux.
First confusion
- Haveno is the software used, it comes with a testnet for trying it and the software releases are basically useless apart from trying it out.
- RetoSwap is the haveno app but connecting to the monero mainnet, allowing to actually buy monero. But the RetoSwap app is called Haveno when installed!
Installation
I installed the .flatpak application from the latest Github release. You need to setup flatpak and flathub before.
There are many ways to install it, for ease of sandboxing and graphical configuration I recommend the .flatpak file.
TODO: Verify the download! There is a .sig file but I didnt find their key yet
You can install the .flatpak file from a graphical app store by opening it with that, or via
flatpak install appname.flatpakfrom the terminal.Once installed, it will appear in your app menu.
Wallet
Opening the app, it creates a trading wallet for you. This will receive the monero you buy and you can pay from it directly, or transfer to a personal wallet first. But the wallet is not protected with a password yet!
Backup
It is important to back up the wallet first, then encrypt that backup, for example using an AES encrypted .zip archive, or the tomb utility, or gpg/sequoia or many other ways.
That backup is apparently important, though I was able to load the wallet in feather wallet just using its seee and creation time.
Password
Now create a wallet password. You will need to enter it every time you open the app, and to unlock the wallet when using it in another sofware like Feather or Monerujo.
Credentials
Store the following in a password manager like KeepassXC:
- seed
- creation time in ISO format, like 2026-01-30
- password
These are essential, especially the creation date which can be easily forgotten. Otherwise you will not be able to retrieve your trading wallet and lose any amount stored on there.
Payment
Now you can configure any payment method you like, if it is supported. As far as I understood, these are all methods where you actively pay a person, like Bank transfer, Paypal, Wise etc. I do not know if you need to configure one if you just want to pay, as the XMR seller should mark a payment as sold, while the exchange has no insight.
Buying XMR
Important: to buy XMR, you need XMR! So if you start with zero, try to get XMR from a friend, or use another exchange like Bisq (not sure if possible) or the many centralized ones.
Haveno requires to spend monero intermittently, the most amount is used as deposit, while a small amount is the transaction fee.
Depending on the lowest available offer, you need more or less XMR to start. You can pay the XMR from your trading wallet or an external one, and then use the bought XMR to fund bigger payments.
Buying XMR is pretty straightforward, while I haven't understood the signing and trust system yet. You may preferrably buy from long existing sellers with a checkmark next to the account.
Initiating a payment, you can select the amount of XMR. You can use this to buy just as much as your existing deposit allows. Be sure to check the price per XMR, some people might try and rip you off!
After having started a payment, expect to wait over an hour for the payment to be confirmed on many monero nodes (afaik). This improves safety by storing that info further in the blockchain. From this point on (afaik) you cannot cancel a payment, or otherwise weird things may happen.
You may open the trader chat to contact the seller and discuss if you need to enter a specific payment reference for example.
Once the seller receives your payment, your XMR will quickly arrive in your trading wallet.
Using the XMR
I dont know the issues with using that wallet to pay directly. Sending the XMR to your personal wallet involves a small transaction fee though.
You can directly import the wallet in Feather, Monerujo or other wallet apps, where you can use it to send and receive XMR. Make sure to store the credentials and store the password manager backup file in multiple places!
I succeeded in using Haveno (Called RetoSwap when used on the mainnet). It was quite confusing so I will document the TLDR here and give a guide about the use on Linux.
First confusion
- Haveno is the software used, it comes with a testnet for trying it and the software releases are basically useless apart from trying it out.
- RetoSwap is the haveno app but connecting to the monero mainnet, allowing to actually buy monero. But the RetoSwap app is called Haveno when installed!
Installation
I installed the .flatpak application from the latest Github release. You need to setup flatpak and flathub before.
There are many ways to install it, for ease of sandboxing and graphical configuration I recommend the .flatpak file.
TODO: Verify the download! There is a .sig file but I didnt find their key yet
You can install the .flatpak file from a graphical app store by opening it with that, or via flatpak install appname.flatpak from the terminal.
Once installed, it will appear in your app menu.
Wallet
Opening the app, it creates a trading wallet for you. This will receive the monero you buy and you can pay from it directly, or transfer to a personal wallet first. But the wallet is not protected with a password yet!
Backup
It is important to back up the wallet first, then encrypt that backup, for example using an AES encrypted .zip archive, or the tomb utility, or gpg/sequoia or many other ways.
That backup is apparently important, though I was able to load the wallet in feather wallet just using its seee and creation time.
Password
Now create a wallet password. You will need to enter it every time you open the app, and to unlock the wallet when using it in another sofware like Feather or Monerujo.
Credentials
Store the following in a password manager like KeepassXC:
- seed
- creation time in ISO format, like 2026-01-30
- password
These are essential, especially the creation date which can be easily forgotten. Otherwise you will not be able to retrieve your trading wallet and lose any amount stored on there.
Payment
Now you can configure any payment method you like, if it is supported. As far as I understood, these are all methods where you actively pay a person, like Bank transfer, Paypal, Wise etc. I do not know if you need to configure one if you just want to pay, as the XMR seller should mark a payment as sold, while the exchange has no insight.
Buying XMR
Important: to buy XMR, you need XMR! So if you start with zero, try to get XMR from a friend, or use another exchange like Bisq (not sure if possible) or the many centralized ones.
Haveno requires to spend monero intermittently, the most amount is used as deposit, while a small amount is the transaction fee.
Depending on the lowest available offer, you need more or less XMR to start. You can pay the XMR from your trading wallet or an external one, and then use the bought XMR to fund bigger payments.
Buying XMR is pretty straightforward, while I haven't understood the signing and trust system yet. You may preferrably buy from long existing sellers with a checkmark next to the account.
Initiating a payment, you can select the amount of XMR. You can use this to buy just as much as your existing deposit allows. Be sure to check the price per XMR, some people might try and rip you off!
After having started a payment, expect to wait over an hour for the payment to be confirmed on many monero nodes (afaik). This improves safety by storing that info further in the blockchain. From this point on (afaik) you cannot cancel a payment, or otherwise weird things may happen.
You may open the trader chat to contact the seller and discuss if you need to enter a specific payment reference for example.
Once the seller receives your payment, your XMR will quickly arrive in your trading wallet.
Using the XMR
I dont know the issues with using that wallet to pay directly. Sending the XMR to your personal wallet involves a small transaction fee though.
You can directly import the wallet in Feather, Monerujo or other wallet apps, where you can use it to send and receive XMR. Make sure to store the credentials and store the password manager backup file in multiple places!