Memmy - An iOS client for Lemmy

5074 readers

1 users here now

View on GitHub

Join the Discord

Code of Conduct

founded 1 year ago

MODERATORS

gkd@lemmy.ml

Sean@beehaw.org

teflocarbon@lemmy.world

sgriff@lemmy.ml

ktgd@lemm.ee

Issue subscribing to communities (lemmy.world)

submitted 1 year ago by BlueDepth9279@lemmy.world to c/memmy@lemmy.ml

4 comments fedilink hide all child comments

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.

top 2 comments

sorted by: hot top controversial new old

[–] CosmicSploogeDrizzle@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] BlueDepth9279@lemmy.world 0 points 1 year ago

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.

load more comments