PriorProject

It's already been bumped: https://lemmy.world/comment/89876.

Yeah, I'm not a mod or admin. There's probably some etiquette here but I have no insights.

Check https://hakbox.social/modlog while logged in as admin. You ought to be able to see who is executing moderation actions there.

I don't know a lot about moderation/admin, but I believe mod actions federate around the network, at least by default. So probably an admin or community mod on an instance you federate with blocked those users and the ban federated to your instance.

Nothing wrong with that, admin'ing an instance is a pretty serious job. I wonder how many instances will fold once they realize what they really signed up for. I lucked out in finding a new Lemmy instance from an experienced mastodon admin team so I have some faith that they're not in for a rude awakening.

Whether or not they have signups disabled, lemmy.ml isn't a good instance to sign up for. It's the biggest, and is "too big" for the hardware available to the admins, as described in https://lemmy.ml/post/1147770. Join-lemmy.org has other options. Good choices have 100 - 1000 active users. Above 1k active users and you're at the leading edge of being on one of the biggest Lemmy instances that has ever existed and are in danger of experiencing lag and other performance problems as people continue to pile on.

Awesome hardware report. If my instance starts falling over too hard I'm definitely considering setting up my own and this is great info to help me size it properly... though my admins lived through the mastodon twitterpocalypse with 4k signups per hour so if anyone can keep the lights on through this madness I'd think they have the experience to do it.

It is possible that nginx or some other http proxy is forwarding requests via some borked virtual host or url rewriting config, such that requests are arriving at Lemmy tagged with the old name?

Perhaps the affected user could clear some browser caches as well to ensure there is nothing funky going on in their specific browser.

Hot ranking was identified as a problematically slow query in https://github.com/LemmyNet/lemmy/issues/2877. Maybe it's possible that it's timing out on the postgres backend and you're getting partial results.

I see you're a fellow lemmy.world user, you could crosspost to !lemmworld@lemmy.world and possibly at-mention Ruud or one of the new admins listed in https://lemmy.world/post/28012 to see if they anything funky going on in the logs.

My prediction is that there's nothing you can do about this personally, though, other than report it to admins and provide any information they request.

• lemmy.world started on a 2vcpu/4GB instance which worked until it was like maybe about 1k registered users / 300 active users. It since scaled up to 4vcpu/16GB: https://lemmy.world/post/22070
• lemmy.ml ran on 4CPU's until it was like 30k registered and 1k active: https://lemmy.ml/comment/451028.
• sh.itjust.works runs on pretty big hardware, but they actually posted resource utilization graphs: https://sh.itjust.works/post/4706. I think they were maybe 100 registered users and 20-50 active at the time this was originally posted (they're one of the fastest growing instances and are much much bigger now). Seems like maybe 1G of ram usage?

These are all big instances, but they show that lemmy doesn't take THAT much hardware even for hundreds or thousands of users. I don't know exactly what lemmy scales down to for a single-user instance if that's what you're after. But requires a postgres db and 3 other processes (lemmy, lemmy-ui, and pict-rs). It seems likely that 1CPU and between 512MB and 1GB of ram would be somewhere near the minimum resource requirements. Not sure about disk-usage, I haven't seen anyone discuss it.

For you, @SlimyRat@lemmy.ml as a lemmy.ml user, lemmygrad.ml isn't blocked, search for lemmygrad on https://lemmy.ml/instances to confirm. Other instances (like beehaw and sopuli) did defederate with lemmygrad. Lemmygrad is a topic-oriented instance (or at least an instance with a very strong cultural backdrop) of radical leftism. Not the mainstream liberal progressive left, but like Marx, Lennin, socialism, communism, radical anti-capitalism. Users on instances with cultures that lean in liberal progressive directions often clash strongly with users from this instance with a strong radical left culture.

This culture clash regularly causes flamewars and moderation shenanigans. As a result, some instances defederate with lemmygrad. But again, lemmy.ml is not such an instance and lemmygrad is not blocked for you.

I responded to cameron with a meatier comment, but I'm at the limit of my knowledge and doubt I can do much more personally. But it does look to me like this is something cameron will have to sort out server-side, I don't think there's anything you can do about this as a user other than help them as best you can by testing or providing requested data.

I'm beyond the limit of my knowledge and don't think I can be any more help here.

The one thing I do notice, is that the language of that error message seems to suggest that your own instance is regarding some of this traffic as invalid traffic from a federated peer? I'm zooming in on cannot accept local object from remote peer here, which makes it sound like your lemmy instance is misidentifying itself somehow. This makes me think about potential DNS mismatches, are you running lemmy and lemmy-ui in docker containers? Could lemmy-ui be identified by one name in configs, but reverse-resolve to a different name from within the lemmy docker container? I'm speculating wildly here and I'm not sure what I'd even do with the answers to these questions. Just thinking out loud.

Maybe someone else who has actually admin'ed a lemmy instance will weigh in. There's certainly a lot of useful data in this thread that might allow another lemmy admin who has seen this to chime in. You could also consider cross-posting to https://lemmy.world/c/lemmy_admin@lemmy.ml for more visibility.