[SOLVED] Why won’t my small Lemmy.world communities show up on Lemmy.ml?

Spec_OpsFive@lemmy.world to Technology@lemmy.world – 22 points –

I created two small communities on Lemmy.world, one is Militaria Collecting, and one is called Unforgotten. Following the recent hack, I decided it would be best to have several moderator accounts on different instances. As I am searching for these communities on Lemmy.ml on my alt, it won’t show up. I have tried troubleshooting, but it isn’t working. Why is this, and what can I do to allow my account to join?

This isn’t just an account issue, I fear that my communities are missing out on a lot of potential subscribers if it is unable to be seen. What can I do?

27

You are viewing a single comment
View all comments

Someone from another instance needs to subscribe to communities on your instance before they show up.

If nobody from Lemmy.ML subscribed to your communities, they won't show up there. You should be able to go to them directly with

Lemmy.ML/c/<your community>@<your instance>

Edit: They may use a different directory than /c/; use whatever format the instance would normally use for a community URL, just remember to add the @instancename after the community. You may also need to put an exclamation point (!) At the beginning of the community name. Every instance seems to be just a little bit different in this regard.

Then you can subscribe to them with an account on Lemmy.ml.

Confirming that this is the way it works (at least on kbin). I just did a test run with militaria_collecting@lemmy.world on Kbin.social. At first it doesn't show up and I get a 404. I then follow @Spec_OpsFive (who does exist on kbin.social via this thread that was federated there), and search again - it now shows a newly created magazine (aka community) with no posts, and I'm allowed to sub:

https://kbin.social/m/militaria\_collecting@lemmy.world

So yeah, someone has to subscribe to either the user or the magazine for the instance to start recording content from it. Once that initial step is in play, your instance records the incoming posts from the federated community.

Returns a 404. It doesn’t work on lemm.we either, probably due to the same reasons. I have tried that instance too, isn’t working. Any other suggestions?

Returns a 404. It doesn’t work on lemm.we either, probably due to the same reasons. I have tried that instance too, isn’t working. Any other suggestions?

Do they actually need to subscribe or do they just need to search it up?

I'm on a smaller server that has quite a few 0 subscriber instances.

Just search

!community@instance