Probably some hack to make it look to the OS like it is charging the battery.

But yeah, why all the silicone? 😱

SteamOS is arch based, but not arch. We will see how far this will affect upstream, but since SteamOS mainly focusses on Flatpak for apps, there is no real need for a huge ARM repo.

The sideload APK think might have been speculation, or do you have a video with a Valve employee saying so? It could certainly work with Waydroid and some tinkering, but probably not for Android VR games that AFAIK depend on some proprietary Meta stuff most of the time.

So uh, ahem.

Yes.

Valve can indeed count to three.

No, the Steam Controller doesn’t fully count. This is 2.5 at best.

And see how the Steam Frame only has two screens and not three?

No, they could compile Steam for native ARM and launch the x86 games via FEX from within.

Remains to be seen which way they go, but I see no big reason why they would not do that.

Kinda missed opportunity to call it the companion cube 😅

But I am sure there will be a custom skin for it that will make it look like one.

Looks pretty promising and no huge surprises. Will be interesting to see the price points of each.

It looks fine as in the default Piefed theme, yes. But they used to have a very nice custom theme.

Their theme broke with the update?

Probably? I have not tried it myself to be honest.

I am not sure how intercompatible the modules are. It might be that you have to chose between them.

It is a modular system that includes a module for microblogging. But it can also be turned into something else.

Recent models run surprisignly well on CPUs if you have sufficient regular RAM. You can also use a low VRAM GPU and offload parts to the CPU. If you are just starting out and want to play around I would try that first. 64gb system RAM is a good amount for that.

It also further links to another issue about individually blocking users and communities. Apparently that is quite inefficient in the current version, so maybe that adds to your problem?

What you can try is to clear your browser cache for the main domain. In the past there was a bug in Lemmy that caused Firefox based browsers to accumulate many gigabytes of cache data and that slowed down the loading of the page significantly. In the latest version there are some fixes for this and it shouldn’t effect app usage, but I suspect this problem still persists to some extend.

Aside from general issues others have mentioned, our instance (slrpnk.net) is seeing some especially high database load in the last couple of days and I also noticed the subscribed page to be even slower than usual. I tried to figure out what it causing it, but so far there is no clear smoking gun, but I suspect some AI scrapers found a way to target the Lemmy API directly so our current scraper protections for the webinterface are inadequate.

There have been such attempts, like Nextbox for example. But afaik they have been all commercial failures, IMHO because basically anyone that cares enough about this stuff can build their own for a much lower price, and those that don’t…

Indeed, Postgres 18 introduced some breaking changes and AFAIK Lemmy isn’t compatible with them yet. This will probably be fixed in the next release.

https://github.com/YoRyan/mailrise

Is something you might be interested in.

With libvirt it is fairly easy yes. And you can also install a standalone web-gui like Cockpit or use the desktop app virt-manager over ssh to do it.

Uff, big difference! Nice job 👍