Keep in mind that these are the early days of Lemmy and the admin is donating time and resources to get this community going. Getting the configs published publicly so that people can make informed choices about which instance they wish to use would certainly be nice, but comparing this to Reddit is a bit far-fetched. TheDude is trying to sustain the community as best as he can, whereas Reddit has been suffocating the community in exchange for corporate profits.

Please stay respectful, even if you disagree.

Why wouldn't you want your home media server software running on the server that's in charge of storing your media?

There are many reasons to do so, such as wanting to use GPU acceleration or a better CPU than what your NAS or SAN has to offer.

It depends on the instance you're accessing the content from. Some remove content will still show up from other instances even if I remove it on sh.itjust.works.

Posts in this community should be directly related to sh.itjust.works, not just Lemmy in general. With that being said, I think that the question has been answered thoroughly by the folks here.

Some maintenance done by @TheDude@sh.itjust.works caused issues. If you're interested to find out more you can join us on #sh.itjust.works:matrix.org via Matrix. Long story short; the site image was preventing lemmy-ui from restarting after doing basic maintenance.

For what it's worth this game allowed my partner to learn how to use two sticks at once.

I'll take a look at our configs tomorrow 👍

The majority of these communities were cleaned up by @TheDude@sh.itjust.works tonight but if you spot any more you can DM him or also raise the issue on the Matrix chat that we have here.

We're also working on implementing rate-limiting on our instance so these changes should make sh.itjust.works much less attractive to spammers.

CPU usage has dropped by about half so far, so this is looking great so far.

A lot of bots were spamming the instance which was causing an IO bottleneck, and thus timeout issues. We're looking into solutions to limit their impact, such as rate-limiting users. We're trying to do it in such a way that it doesn't impact regular users which is why it's taking a bit longer.

You might want to clear your site data

https://support.mozilla.org/...

No major changes to the instance, this upgrade really did a lot to optimize performance. We're still seeing some IO spikes here and there but overall performance is much better.