Why YSK: making the most of the fediverse means aggregating content from as many places as possible, but it’s not an intuitive process right now, especially for those using apps like Jerboa or Mlem.
I have been seeing some comments from people struggling to subscribe to kbin magazines from Lemmy so here’s a step-by-step of how I’ve been doing it:
- Note the name of the kbin magazine you want to subscribe to (example: kbin.social/m/books)
- Log into your Lemmy instance from a browser
- The Lemmy instance you are registered with will be the first part of the URL and the kbin community will be the second part. Example: I’m registered with lemmy.world so to register with the kbin Books magazine I would type https://lemmy.world/c/[email protected]
- From there, just hit subscribe and it will start showing up anywhere you’re logged into your Lemmy instance (I use Jerboa).
Hopefully this helps spread the word!
Have them go to search, make sure everything is searching all, and have them put https://kbin.social/m/LucidDreaming as the search query.
There’s a solid chance they won’t be able to see anything posted prior to when they subscribe, but at least that will make the community federate with that person’s Lemmy instance.
They really need to fix that. It shouldn’t require a subscription to federate. That just means that an /all view is wrong and from this thread, we can see it’s a major UX stumbling block
“All” picks up any communities your instance knows about, whether you personally are subscribed or not. My understanding is that once one person from your instance subscribes to something it starts federating, but unless someone does that it stays separate.
While I agree being able to search for communities needs a little help if it’s a brand new community outside of your home instance to make it less confusing, it makes sense from the standpoint of having to tell the community to talk to an external instance by having someone from the external instance subscribe.