Why are half of my communities stuck on subscription pending?
Why are half of my communities stuck on subscription pending?
After nearly a week, none seem to be accepting new members.
This breaks rules 3 and 4 but leaving it here because of the high quality answers.
It's just a UI bug. You're subscribed. Probably doesn't help lemmy has been overwhelmed by new users and activity.
Unfortunately it's not a UI bug - the UI is correctly showing this message when the target instance has not confirmed your subscription. Most likely this is caused by an overwhelmed instance on one side of the federation.
That's interesting. I've had a few communities show as "pending", but they still appear under my subscriptions view on my home page.
You're right that it's not a UI bug, but it's essentially as consequential as one. You're still subscribed in that the community appears in your feed. The community just doesn't include you in it's "subscribers" list because it hasn't updated it yet
https://www.youtube.com/watch?v=IP-rGJKSZ3s
Your server sent the subscription request to the community's server, but the acknowledgement never made it through amidst the chaos of federation. You're still subscribed.
I have to disagree with those saying its a UI bug. I have been trying to subscribe to the Linux.ml community for 2 days now. I have tried the double tap trick. It never actually changes from pending.
Ive tried over 100 times, no luck.
I cant seem to subscribe to any Lemmy.ml communities from Lemmy.world.
Lemmy.ml and kbin.social seem to be stuck for me.
Federation.
When you subscribe to a different instance, it can take time for the subscription to be sent to the server you're subscribing to.
Sometimes, that data never even makes it.
Honestly, "Subscribe Pending" doesn't change much, it will still show posts in your feed, and you can still make posts and comments to the community.
However, like the "subscribe pending" issue, you may end up with some comments showing up, and others never showing up, on the instance you're posting to.
I've had lots of troubles with the random nature of which comments of mine post to other instances. with beehaw and lemmy.blahaj it is seemingly at random if a comment will show up on their instance or not. When I go visit threads on beehaw or blahaj and not through lemmy.ml, sometimes comments show, sometimes they don't. It really is random and just whether or not the data made it through.
These are small servers run by volunteers and they don't have racks and racks of failover servers like reddit. The amount of data passing back and forth between instances is HUGE and it seems like a lot of that data is getting "lost" in the transit, resulting in things like missing comments or "subscribe pending."
These are part of the growing pains of a federated service.
I have subscriptions on lemmy.ml which still refuse to go through after a couple weeks. Just tried resubscribing one of them and it's again stuck on pending. I don't know of any rush of new users happening right this minute so I doubt the server is overloaded, and the community doesn't require moderator approval to be subscribed, so I really don't know what the holdup is. But like OP, I have several that just refuse to go through.
What are the backend protocols for federation? I wonder if it’s true server load (physical lack of compute) or something like network bottlenecks (which we might be able to see by using things like NIC utilization and error rates).
Network bottlenecks may be addressable at the protocol layer with improvements to how federation works.
I'm pretty damn sure its physical lack of compute, because lemmy.ml already massively upgraded their server two weeks ago to account for this, and it's already overloaded again.
Also, this was an issue early on in Mastodon as well. The more federated servers there are, the more each server has to communicate with every other server which apparently eats up RAM and CPU cycles. So each time there's an update, it has to sent it to X number of servers, and retrieve data from X number of servers, and as X climbs, the more network activity and CPU cycles to handle it there is. A lot of requests in waiting can be stored away in RAM, but even RAM has limits.
Finally, the newest server version was supposed to help ease this kind of stuff by moving from using WebSockets to HTTP. Pretty sure the federation protocols are all just HTTP, but I could be wrong.
It's because the remote instance is getting hugged, or is on an older version. You can try unsubscribing and resubscribing which also sometimes helps.
it just looks like you are not subscribed, but you actually are already. What helped for me to get rid of this bug was to just try unsubscribing and subscribing a couple of days later.
This also happens when you try to subscribe to a community on a server that has defederated yours.