It's just a UI bug. You're subscribed. Probably doesn't help lemmy has been overwhelmed by new users and activity.
this post was submitted on 02 Jul 2023
66 points (94.6% liked)
Asklemmy
43372 readers
1586 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
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.
YesβI'm working on a Lemmy client and seeing the same behavior. What is showing in the Lemmy web app UI is exactly what's being returned from Lemmy instances/servers at the moment. Trying to figure out how to display it better to users, but not a whole lot we can do about it right now.
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.
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.
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.
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.
I'm on lemmy.ml and it's slow as hell and half the time errors out and it's been like this for days. They've been under heavy load for a while and I don't know when it's going to taper off. I'm almost positive it's just a lot of data isn't making it to lemmy.ml because it's timing out.
Oddly enough, I just ran across a new community to subscribe to on lemmy.ml, and that one went right through. I also noticed another oddity (which is probably related directly to the subscribe bug)... the first time I click the subscribe button, it turns dark. If I click it a second time I get the Pending message. However for this new community, I clicked the subscribe button just once, then reloaded the page and it said I was subscribed. Going to try that with some others and see if I have any better luck.
[EDIT] I do seem to be making progress now by reloading the page. The first one took some time, and it seems like subscriptions are going slowly no matter what server they're on right now. I've seeing several that don't even show the subscribe button until I reload the page again a few minutes later but I've been able to get fully subscribed to all the groups I've checked again so far.
For me, it only happens with Lemmy.ml. Whether subscribing to a Lemmy.ml instance, or a Lemmy.ml user subscribing to another remote instance. No issues with other instances, regardless of version.
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.
This breaks rules 3 and 4 but leaving it here because of the high quality answers.
I took a look at rules 3 and 4 and can't see the violation. What is it so I don't do it again?
This is more of a support question than an open ended discussion question. It really belongs on [email protected]
Here's the other very similar thread: https://wayfarershaven.eu/post/58114
Looks like the other examples have already been removed.
Really, though, #3 about support is the bigger reason.
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.
It's just a UI bug. You're subscribed. Probably doesn't help lemmy has been overwhelmed by new users and activity.
view more: next βΊ