You should know that the issue with many communities on other Lemmy instances that you subscribed to showing a “subscribe pending” status has mostly been resolved.
I looked in my subscribed communities list, found all the pending ones, opened them, unsubscribed (clicked the yellow “subscribe pending” button) and resubscribed. After that, I refreshed the page and I was now fully subscribed to them, regardless of which Lemmy instance hosts the community.
The only exception, unfortunately, was with kbin communities. All the kbin.social ones still showed subscribe pending for me even after following the same procedure. Still, this is a big improvement over having a bunch of half-subscribed communities.
I know that the pending status didn’t have much of a negative effect on my end because I would still get those in my subscribed feed, but I hoped for the communities’ subscriber numbers to fully reflect the actual number of subscribers.
I was not aware of this. Sorry to hear, and I hope everything gets better for him.
It’s been forked by the community. It’s called mbin and fedia already switched over.
Interesting, thanks. I had seen mbin mentioned a couple of times, but didn’t know the story.
If you want more context, Ernest, the kbin dev, went into some detail of the troubles.
Thanks.