I’ve noticed that I can’t subscribe to certain communities. For example if I search for Memmy and click on subscribe, the heart goes from an outline to a filled heart and I get a notification that I subscribed to memmy.
However, if I exit the Memmy community page and then re-enter, the heart is back to just an outline as if I’m not subscribed and it doesn’t show up in my subscribed communities.
Not sure if it’s a Memmy problem or a federation problem. My account is through Lemmy.world, have consistent problems with Beehaw and Memmy is on Lemmy.ml.
You must log in or register to comment.
Same here. On the web app the community is listed as subscribed, but not in Memmy. Maybe an API thing.
I think it’s related to the issue I reported here. Are they the communities hosted on a different instance to where your own profile is hosted?
No, communities from all over the instances are listed, but not all of them. I can’t see any pattern here.
What community you were trying to subscribe to? Dev can only troubleshoot if you give more detailed information on the issue
I know that beehaw.org users can see but not able to interact (upvote/comment/save) with lemmy.world becaused they blocked lemmy.world. Not sure if the other way is allowed
Maybe try subscribe to a lemmy.world to see if it works
Memmy@lemmy.ml, nfl@lemmy.world, starfield@lemmy.zip, programming@beehaw.org for example.
But I’ve been able to subscribe to communities in most of these instances as well. I assume it’s larger than Memmy, but since that’s the main app I’ve been using I thought I’d post and see if anyone else has been having issues.
I tried all 4 and it seemed to work. All 4 shown up in my feed. Except programming@beehaw.org was out of date, with only 2 comments on the latest post vs actual 18 comments (I saw using beehaw account). See above comment for more
Lemmy.world and beehaw dony work together. You’ll only see cached posts and comments from one to the other. Beehaw decided to wall off their garden from world and sh.itjust.works
As for Lemmy.ml, there is definitely issues with cross Instance Syncing. Lemmy.ml is rolling out BE 0.18 release client updates at the moment. 0.18 brings some major changes. On the website when subscribing to lemmy.ml communities you often get the “pending” status rather than “joined”
Hopefully when full 0.18 rolls out to all instances these issues will be fixed. World and other instances re still on 0.17.4
Yeah I read about the Beehaw decision so I wasn’t sure if that impacted subscribing to communities in their instance as well. I didn’t think much of it till I had issues subscribing to Lemmy.ml and even communities in Lemmy.world.
Sounds good, appreciate the info. I’ll hold tight and see if 0.18 update fixes the issue.
