It looks to be some kind of bug. Even though it shows as pending the communities still show up in my subscribed feed. I guess it’ll sort itself out over time.
Meta (lemm.ee)
lemm.ee Meta
This is a community for discussion about this particular Lemmy instance.
News and updates about lemm.ee will be posted here, so if that's something that interests you, make sure to subscribe!
Rules:
- Support requests belong in !support
- Only posts about topics directly related to lemm.ee are allowed
- If you don't have anything constructive to add, then do not post/comment here. Low effort memes, trolling, etc is not allowed.
- If you are from another instance, you may participate in discussions, but remain respectful. Realize that your comments will inevitably be associated with your instance by many lemm.ee users.
If you're a Discord user, you can also join our Discord server: https://discord.gg/XM9nZwUn9K
Discord is only a back-up channel, !meta@lemm.ee will always be the main place for lemm.ee communications.
If you need help with anything, please post in !support instead.
happening on lemmy.ml communities for me. lemmy.one communities seem fine for me.
edit: its also happening to me on communities outside lemmy.ml now
I'm still wondering on this. I suspect it has something to do with refreshes between instances - as if this instance isn't yet away of that community. It's always in foreign instances, regardless.
I had a few that didn't work, then I tried them again a day later and they went through. However I've had others on major instances that still haven't come in (eg /c/asklemmy@lemmy.world).
I'd love to hear @sunaurus' opinion on this.
I'm seeing this especially with lemmy.ml communities. The consensus is that it's due to latency, but what's weird is if I cycle the subscription it may go through instantaneously. It's looking more like a bug to me or maybe a combination of code issues and latency.
You'll probably find posts from those communities show up in your sub feed just fine. Seems like it's just a visual bug but you are actually subscribed.
Yeah I understand it still works even if it states subscribe pending, but still it's misleading.
I think it's more than just an instance failing to respond. I mean if it hung for a bit then changed eventually that would be acceptable, but it gets permanently locked in that state, smells of a bug.