How wrong were you. Lot's of people don't want to use wayland until it reaches a certain feature-complete maturity. I for instance have again put it off for another year and won't consider running a wayland only DE at all for the forseable future since it breaks too many things for no good reason and I need to be able to switch back to X11 if needed. I use my pc for for work, not just as a troubleshooting toy.

Taking the topic into account of people moving from old school Windows 7 to this Windows-like distro, these people will probably be more pleased by X11 (hassle free screen sharing, global shortcuts) vs the wayland "in theory it is great and modern but in practice there still are way too many incomplete and missing pieces" situation.

Having said that, the novelty is questionable since the projection is pretty well-known and creating a functional proof of concept that solves many of the patent's problems likely takes a day or so. But I'm not a lawyer so what do I know in this department?

I'm all for people switching to wayland but there should be choice and xorg should not be neglected for ideological reasons.

Looking at it from a distance indeed may raise some brows.

Company instructs you to code something (on your own or using AI) -> they own it

You instruct an AI to code something -> you own it

An AI has become sentient and self aware -> the AI owns it

For the last few days I have been monitoring journald with iotop and found in my case storage use was not excessive at the moment. And there are rate limit options, but I'd really like there to be system-wide filtering options.

For servers I rarely see journald persistence enabled while it is actually very valuable for debugging crashes and other issues. Way easier than regular log files. Though also more fragile and more difficult, so improvements are very welcome.

Am a bit vague on the details but sometimes a driver goes bezerk and starts logging many times per second, e.g. a bug in amdgpu after resume from suspend. Took a while to get that filtered which luckily was only possible because it were kernel messages (dmesg), but for a while I had to disae persistent kernel logging which is dat from ideal.

I get that for certain core parts simplicity is more important than features. But journald is just too basic to enable persistent storage but I also don't want to switch it off.

Quick comparisons: my DDR4 ram is x2-ish (64GB - 342 -> 648 euros). my HDDs are x2-ish (22TB - 548 -> 988). A new _budget_ GPU I bought end of last year is now +100 euros (just half a year later).

Didn't bother to check the SSD since I mostly need it for the OS and they don't die that often, but that comparison should also not be fun. My current build should last till 2030 so hopefully should be okay if nothing breaks, though I am doubtful these prices are coming all the way down again. Either wait it out, pay about 50% more or lower the capacity by 50%.

The list of shortages and price _gauging_ for the last years is pretty extensive: PS5, Xbox, GPU (first bitcoin, now AI), RAM, HDD/SSD, etc. These shortages are becoming an incessant pain in the ass, on personal computing level but also professionally since replacing hardware is becoming difficult and the cloud bill will only go up too. Well at least we have not been replaced by the clankers, yet.

And these authoritarian politicians will destroy the internet with these actions. Maybe they will even change society as we know it, and not for the better.

The problem is thinking such initiatives will achieve anything in a bureaucratic system devoid of honest debate and actual democracy.

These citizen's initiatives must at least be tried but simultaneously we must create a new internet forever out of politician reach.

But it helps against account sharing, err I mean they make database leaks irrelevant except for private info of the customer, err I mean that we can now send more mail to the customer about new AI features without risking they think it is phishing, err I mean this is the easiest measure for the auditor findings so since we implemented this we don't need to fix all the crappy internal api auth problems and atrocious out of date dependencies, err I mean...

The angry one is Ludwig van Beethoven.

I guess of the designs with people I only like designs E and F. There the expressions don't look too odd. Takes some getting used too though.

And what are the options they give? I guess historical people with weird abstract community settings or birds with office buildings. Is that all the EU represents?

Whatever they go for I hope they do not open the can of worms that is historical people, or any people for that matter. It will start all kinds of tiresome discussions and people will draw on them making it difficult use defaced bills.

If you really want historical people as a gesture of appreciation or celebration of their achievements then make that a limited edition.

Seriously, there is something tremendously wrong with governance when politicians keep changing the whole world around us, without us having any say in it at all. The threat this measure poses to the internet and society is significant, yet it is being pushed through without any substantial debate or push back. This just is not how decent and actual democracies should function. What messed up timeline is this?

But would you really store new material encoded in Vorbis just to be able to play it on an old device? Vorbis can sound fine, even at lower bitrates like 128k or 96k, but Opus would sound much better. So perhaps then use Vorbis at higher bitrates like +192k? I prefer Vorbis to Aac but at that bitrate minor intricacies of the container format become more important than the codec because audio quality wise they are near indistinguishable.

Why? Care to explain?

I have fully switched to opus for lossy since I cannot be bothered to find the sweet spot for aac encoders and bitrate. Opus simply is too good and convenient and has been for ages.

What other lossy codec is better and for what reason? Under what circumstances and use cases? I really need put effort in looking for edge cases to not choose opus.

Aac is good too, but way too many choices to make for storing mass material for the long term and be sure the quality is always good enough.

Still having a good quality and default aac encoder is great. Though I don't get why it is mainly CBR.

And if all the IPv6 endpoints of a major service go down we should pin our mtu to the bare minimum? Nonsense.

The inconvenient truth is that IPv4 will be more stable than IPv6 until the former gets demoted to second class fallback protocol instead of the major driver of the internet. And when that happens no one knows.