this post was submitted on 27 Jun 2023
20 points (95.5% liked)
sdfpubnix
1316 readers
62 users here now
Fans of SDF
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I went down this rabbit hole this morning. There was a bug pre version 0.18.0 which caused this when subscribing to a federated community. If you go through and unsubscribe and resubscribe this should fix the issue. I did this myself and it fixed all except one which, unfortunately, is from lemmy.world. I am wondering if their instance is having an issue or if maybe they're on an older Lemmy release which is causing an issue.
I only have this problem with lemmy.world as well. Strange, since they've upgraded to 0.18.
Both of the ~~subs~~ communities I have this problem with are on lemmy.ml. But one of my other lemmy.ml subscriptions works fine as does lemmy.world. 🤷
I think it's related to overloaded instances. I got up real early (CEST) when Americans are mostly asleep, and unsubscribed + resubscribed to the "pending" lemmy.world communities, and now I'm properly subscribed. This did not work during "prime time" yesterday.