TL;DR: questions:
EDIT: I’m not aking how to fix it for a single community, I’m asking how to handle it for >200 subscriptions (thanks!)

  • If a community says “Subscribe pending”, is it possible that their posts do not appear on the feed?
  • If the answer to the previous question is yes: is there any script to fix “Subscribe pending” issues on batch?

Long version:

I started using Lemmy some days ago and when subscribing to some communities (on other instances) I got the “Subscribe pending” message. I’m aware it’s a common issue (see search for Subscribe pending in this community) but, because what I read is that the bug was the message itself (but you were indeed subscribed) I ignored them.

Today I took a look again at the issue and I saw that some people recommend un-subbing and re-subbing again. The thing is, now I’m subscribed to more than 200 communities, so it would take a while to do it manually.

Thanks!

  • D_GEnglish
    8•1 year ago

    On desktop I’ve found if I leave the community page opened for a few minutes, when I get “Subscribe Pending”, and reload the page, it changes to “Subscribed”.

    • 1024_KibibytesEnglish
      4•1 year ago

      I wait a few seconds and then reload the page. That usually works. Sometimes I have to unsubscribe, wait 5 seconds, re-subscribe and then reload the page.

    • @[email protected]English
      3•1 year ago

      Some times you have to unsubscribe, then subscribe again and then reload the page.

      Unfortunately I have still experienced syncing problems with some communities even after having fixed the subscribe pending issue. !bookcollecting[email protected] still shows up with 0 comments for me on all the posts, even though I know there are lots of comments.

    • @CrulOPEnglish
      2•1 year ago

      Thanks for the info, but I’m not asking how to fix it for a single community, I’m asking how to handle it for >200 subscriptions

      • @PriorProjectEnglish
        1•1 year ago

        Not to be glib, but the way you fix >200 communities is the same way you fix the first one, and then do it >199 more times.

        It’s broken and it sucks. People have articulated the hacky workarounds that sometimes work for them, there’s no bulk version of that process that I’m aware of. You either ignore it, bang on it one community at a time until it’s fixed, or become a programmer and fix it for everyone (or script the hacky workaround).