I know there were some oddities about this but I can’t find the previous discussion I had seen on the matter. I am subscribed to a handful of communities from when I joined here on sh.itjust.works, but it’s not consistent. Several communities appear fine in my feed despite my “subscription pending”.

But for new communities, the “subscribe” button is not actually a button, regardless if they’re here on sh.itjust.works or elsewhere. I could theoretically subscribe from the list of communities, but I’m interested in looking for communities on specific topics and I expect I could be scrolling for days before I find them. As soon as I use the search feature, I’m given a list without a column of “subscribe” links and I’m back to square one with needing to navigate directly to that community.

Am I the only one experiencing this? Is the source of this problem known? I’ve been advocating patience with the growing pains the threadiverse is likely to experience, but this is a really critical part of the experience that’s not working. I know I might be in the minority but I’m not here to scroll through the all-page.

  • @tallwookie
    link
    fedilink
    English
    28 months ago

    yeah, I’ve run into that a time or two - or the subscribe button is a button but it doesnt “act” like a button. it’s just bizarre behavior I’ve never really seen on any other platform. I can still interact with those pages/communities, just not add them into my feed by “subscribing”.

    • @[email protected]OP
      link
      fedilink
      English
      48 months ago

      I’ve been getting the best results by toggling the page between posts and comments. This forces the UI elements to reload and subscribe becomes a real button. It won’t update, though: I’ll have to click it and then reload the page, and generally it appears either as joined or subscribe pending. I intend to go through and fiddle with the latter at a later time, as you can force the matter by repeatedly leaving and re-subscribing, but I’ve been made to understand this is a server load issue.