Literally nothing happens.

Linux init conservatives: Alright that’s the final straw, systemd!

I hate posts where the question is the top (or only) search result and the answer is some dickwad saying “did you try Googling first, smh”.

This is such an incredibly naive take that has already been proven wrong by multiple publishers going out of their way to do exactly what you just said. There’s also a ton of abandonware which is not being sold and never will be again.

Yes, thankfully the reasonable tech companies offering these services have decided to stop the training process after it was done once. The insane increase in energy consumption and hardware manufacturing for datacenter components and accelerators is purely coincidental and has nothing to do with demand for gimmicky generative AI services. Let’s also conveniently ignore the increasing inference cost of more complex models, while we’re at it.

It’s only missing every ingredient except Eier.

I wouldn’t recommend Docker for a production environment either, but there are plenty of container-based solutions that use OCI compatible images just fine and they are very widely used in production. Having said that, plenty of people run docker images in a homelab setting and they work fine. I don’t like running rootful containers under a system daemon, but calling it a giant mess doesn’t seem fair in my experience.

That’s exactly why they’re changing the license. The problem with Swanstation are the developers. Retroarch in general has some pretty horrible people maintaining it and this isn’t the first time they’ve harassed an emulator dev over nothing.

I think this is the natural conclusion to modern social media. Constantly being confronted by a billion different worldviews and farming people for engagement by showing them things they disagree with is just going to breed extreme echo chambers.

This type of behaviour is neither new, nor actively harmful. There’s really nothing you, I or anyone else can do to stop it, so the only remaining choice is to ignore it and not post screenshots in different communities where people agree with you.

C has not aged well, despite its popularity in many applications. I’m grateful for the incredible body of work that kernel developers have assembled over the decades, but there are some very useful aspects of rust that might help alleviate some of the hurdles that aspiring contributors face. This was not a push by rust evangelists, but an attempt to enable modernization efforts at least for new driver development. If it doesn’t work out, that’s fair enough but I’m grateful for the willingness - especially of Linus - to try something new.

If I may ask: how practical is monitoring / administering rootless quadlets? I’m running rootless podman containers via systemd for home use, but splitting the single rootless user into multiple has proven to be quite the pain.

The whole premise of this discussion was about technological progress and growth going by your initial comment. That means refining existing models and training new ones, which is going to cost a lot of energy. The way this industry is going, even privacy conscious usage of open source models will contribute to the insane energy usage by creating demand and popularizing the technology.

Do we really need to grow our energy consumption as a society by such a disproportionate amount?

I remember reading somewhere that it would be the farthest manmade object from earth, far outpacing the Voyager spacecrafts, assuming it didn’t vaporize.

With bluray rips, I don’t really see any way to avoid that unfortunately, unless someone else has already added the hashes for your release. Most people use it to scan their encoded releases, which will (in most cases) have already been added to AniDB by the release group. I’m a bit surprised though, that none of your rips are recognized. Have you checked the AniDB pages for your series to see if anyone uploaded hashes for bluray rips?

Grouping seasons into a series folder doesn’t work well in some cases, because that’s not the way they are released in Japan. A new season is (most of the time) effectively an entire new show entry. Show seasons are mostly a north american thing. No matter which software you use, there’s always going to be some minor issues if you group seasons into one entry.

Shoko compares a files ED2K hash against the AniDB database. The filename doesn’t matter for automatic detection. Have a look at the log to see if there are any issues. It’s entirely possible that AniDB just doesn’t have the hashes for the raw BluRay rip. In that case you can either manually link them in Shoko, connecting the AniDB episode id to the file hash, or create new file entries on AniDB with your specific hashes.

Shoko also has rate limits. The problem is that AniDB does rate limiting in an extremely stupid way for a UDP API and doesn’t even have the decency to define clear time limits.

The only thing that’s slow is dnf’s repository check and some migration scripts in certain fedora packages. If that’s the price I need to pay to get seamless updates and upgrades across major versions for nearly a decade, then I can live with that.

I tried using connman to setup a wireguard connection once. It was not a good experience and ultimately led nowhere, due to missing feature support.