Performance is not the goal, but cleaner code and more manageable code. But both will ultimately lead to better performance. As of now it was basically impossible to change something in the database structure since it was hard to estimate the impact of it.

... and may also break compatibility with previous 10.Y releases if required for later cleanup work.

If you read through the whole paragraph, it is clear that they mean the compatibility of previous jellyfin versions.

Also, again:

Note however that the 10.Y.Z release chain represents the "cleanup" of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

That means that the code is not cleaned up with that release.

If you would release 11 before the code is considered cleaned up, you would basically break your own defined versioning convention. That is best decided by the active maintainers.

This attack has been known for years now. And tor is simply not able to defend against it without a complete redesign.

A port is not secure or insecure. The thing that can lead to security risks is the service that answers that port.

Use strong authentication and encryption on those services and keep them up to date.

I hate when i have to go 4 links deep to get an explanation of what it even is.

The simple point is, no one forces you to use wires. Bluetooth has been a thing for decades.

But basically every (yes some exceptions) company that makes phones forced you to use wireless ones.

And in the case of Fairphone it is just simply hypocritical.

Let's not forget this here.

https://www.youtube.com/watch?v=bRdL0StldJM

Wired headphones do not have the need for replaceable batteries.

If the CPU died, the PC would not have booted up so far.

Imagine, all the money they are throwing to microsoft put towards a few teams that develops actively on open source projects to support independent and open source infrastructure.

A lot of IDEs would probably throw a warning about unreachable code.

The 3B+ was probably the high of the raspberry pi. It is still pretty much unrivaled in terms of idle power consumption and energy efficiency (or at least i have not seen any other SBC that got below 0.5 Watts on idle) on the consumer market.

But i have trouble investing further into them.

1. They do not post any update guides for newer Debian releases and basically only support new deployments.
2. It looks like they are abandoning their older products. vcgencmd for example is still broken on the 3B+. Since they "fixed" it for the 4B. See https://github.com/raspberrypi/firmware/issues/1224

No you are mistaken with "Or $5 mire to own it". You own a license to watch for the amount of time the platforms decides to keep it up.