this post was submitted on 12 Jun 2023
15 points (100.0% liked)

Mlem for Lemmy

5524 readers
35 users here now

Official community for Mlem, a free and open-source iOS Lemmy client.

Rules

  1. Keep it civil.
  2. This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
  3. We welcome constructive criticism, but ask that it be both precise and polite.

FAQ

Download Mlem for iOS

GitHub

Website

Donate to Mlem

founded 2 years ago
MODERATORS
 

Hello everyone, first post here! I’m trying to get a hang of Lemmy and Mlem at the same time. When I switch my feed to “All posts”, it looks like it’s only showing posts from my local server. Is there a way to see all posts on all servers? Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] AineLasagna@lemmy.blahaj.zone 11 points 1 year ago* (last edited 1 year ago) (2 children)

This appears to be one of the most limiting factors in Lemmy right now and is not unique to Mlem. Essentially, your instance can only “see” communities that at least one user on that instance has subscribed to.

Example: I’m on the lemmy.blahaj.zone instance. I’m not subscribed to !196@lemmy.world, but someone on lemmy.blahaj.zone IS, thus it shows up in my All feed:

lemmy.directory is trying to solve this by subscribing to as many communities as they can find, serving as an “/r/All” for Lemmy as a whole. But you can’t make an account there, so the idea is you browse the directory and subscribe to any communities you like, thus making them available to other users on your instance.

[–] balder1991@lemmy.world 1 points 1 year ago

Also this is how Mastodon works, right?

[–] xHoudek@lemmy.world 1 points 1 year ago

Thanks for the explainer! Looks like I was just confused about how the communities were presented. Not showing the server name alongside the community name made me think that the community was hosted locally