I just rechecked the strange reports I remembered, and in both cases we had a local user being remote moderator, so this seems like the most likely cause.

Yes, this specifically happens with remote communities, for local communities the instance admins see all the reports in Lemmy so that would be normal.

I am not 100% sure if this is related to other local users being moderators of remote communities, but it is the closest guess as the alternative would just random reports being forwarded to us instance admins with no relation to our instance at all.

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.

It’s worth a try asking your current members in a local sticky-post. Just make sure you do a realistic estimation on how often you might not be available so that they know how involved it might become.

Otherwise the people over at db0 are trialing an “armada” concept of sharing admin burdens between instances. So that is also something you might want to consider.

https://github.com/YoRyan/mailrise

Is something you might be interested in.

Finding a fully managed Lemmy server for a similar low price seems unlikely (and K&H have probably under-priced this).

I think it would be more worthwhile to find some additional admins to share the burden and move to some reasonably priced VPS.

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.

Proxmox adds a lot of complexity and a nice GUI. If you are fine with using the terminal, there is really not much benefit from Proxmox and the potential issues from the added complexity are IMHO not worth it. I am not a Proxmox expert though, so take this advise with a grain of salt 😅

Afaik it is a specific implementation issue in Lemmy that causes this. Instances in Australia had problems catching up with lemmy.world because of that.

The federation is mainly about issues / bug reports (the discussions and comments) and being able to make cross instance pull-requests and so on. So yes, it is mostly about communication.

Those work fine with Anubis.

Anubis is fairly stupid in reality. It only checks the request at all if it looks like a regular browser (and thus catches the scrapers that pretend to be regular browsers to hide in normal traffic). If you use an RSS reader for example that doesn’t hide the fact that it is a RSS reader, then Anubis will send it right through.