Reminds me of the time I was working on something for Mercedes but they couldn’t supply me with the computer for testing. I had to go into the super cramped actual car that was parked in a super expensive secure garage.

Left the company and when I went there for a visit I saw that the new guy actually got to test and develope on a computer they had ripped out of a car.

I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.

The main culprit was the database. As far as I’m aware Lemmy is missing some indexes and due to the ORM they used didn’t always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.

The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.

Image proxying wasn’t bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can’t really debug it. My stuff really shouldn’t be taking up more than a few hundred MBs.

I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.

I wish that was it, but what are those unnamed 64 bit Linuxes supposed to be?

And those channels have been talking about Linux for months. Why now such a sharp increase?

Looks sus. Probably a fluke.

RAM. Maybe 32 would have been enough but 64 cost as much as 32 so that decision was easy.

The biggest advantage of Docker is that it’s a little bit easier to manage all the dependencies of a service. And often enough the Docker images come from the official vendor and thus should in theory be configured optimally out of the box and give you timely updates.

But if you don’t have any problems with your current install I wouldn’t touch it.

Don’t know if I can handle something this sexy on my retro handheld.

Same stuff you do on any other instance. Looking at stuff, upvoting, downvoting, posting and commenting.

Control. I’m not beholden to anyone. My server is federating exactly those communities that interest me.

I run an instance just for myself and it was a nightmare on HDD and 16 GB RAM. It was slow as molasses. Supposedly the database layout will be fixed with the 1.0 release that is just around the corner.

Since I upgraded to 64 GB it’s been pretty smooth. Still wild that that is necessary for a single user.

Also, disable image proxying. I have no idea what pict-rs does but it seems to be too much.

You should consider running Piefed instead. It’s not as resource hungry as Lemmy.

I finally finished Spider-Man: Miles Morales and just started Spider-Man 2. Man, that game runs like ass on the Deck while I have to make it look worse than the previous two.

And it actually feels like what I’m experiencing are bugs and not necessarily the Steam Deck’s fault. Stuff like models popping in without animations. I remember seeing pictures of that when it was new. Strange that they didn’t manage to fix it. Couldn’t they just have stayed on the old engine? It worked perfectly fine!

Have you looked at laser projectors? No bulb should be great.

This article is all over the place. It talks about entanglement and for some reason that’s supposed to be linked to superposition.

You will be unaffected.

It’s really hard to decide whether XSLT or JavaScript is worse. On the one hand XSLT wasn’t cobbled together in a weekend. On the other it requires you to write XML and its “arrays” start at 1.

That’s just for those few websites that use their RSS feed as their content source. If they want to keep doing that they can just get a JavaScript library that provides XSLT functionality. The feed itself is untouched.

Xslt has nothing to do with RSS being available or not.

They have this very complex system of presenting you with two links. One lets you access the tiddies, the other sends you to Club Penguin. Impossible to circumvent. But some hackers claim to manage to do it by “reading”.

[email protected]