I just realized that none of the comments or posts I made in the last week from my instance are getting to lemmy.world.
I went to see if I my instance was defederated. No, still showing as connected.
I then went to see if I got blocked or banned. Nope, my username is not showing up in the modlog anywhere.
Is it because my instance is small? I guess not, because I can interact with people and communities from anywhere else just fine.
At the moment, the only plausible explanation I have is that lemmy.world is overwhelmed and dropping messages from smaller instances. They do however everything in their power to keep more users coming up.
Yeah, I get that they were being attacked. I can only imagine that getting DDOS’d is not fun, and worrying about the Schmoes on the smaller instances is not a top concern.
But even in the middle of these constant outages and attacks, the lemmy.world admins are still keeping registrations open? Why? Wouldn’t it be better if they encouraged the users to move out of the instance to reduce the load? Isn’t the whole point of decentralized technologies to be, you know, decentralized?
I shouldn’t have to come here, create an account and make things even more centralized just so that I can tell people that this attitude is hurting the fediverse.
I wouldn’t be so pissed at this if it weren’t for the fact that some many communities were created here and is making this particular instance a crucial part of the fediverse, but the admins seems to be more worried about getting their user count up than the health of the overall system.
Please, admins, the more you go with this unstable federation and open registrations, the more of an incentive you are creating to centralize this further here. Help the fediverse and help yourselves. Close down registrations and focus on ensuring that everyone can access the communities that are being formed here.
I’m not seeing dropped messages. I can see that a comment in this thread made it through just fine. However, I am seeing since around 09:30 yesterday that get requests for comments (and maybe other activities) are being responded to with 400 “not_logged_in”. I’ve quite a few messages in error queue stacking up because of this.
Edited to clarify. The instance is running kbin.
That’s possible because those requests are being blocked to non-logged-in users.
It’s a federation message. For example I receive a federated like message, and so my instance fetches the comment (and all parent comments) if not already present in my DB. It has the correct headers to be activitypub. So it should be allowed.