Instructions for running your own lemmy instance.
For the moment, lemmy.ml is using an explicit allowlist
for instances we federate with. If you currently run an instance, and would like to be added to join.lemmy.ml:
- Let us know either on !lemmy_instances, or commenting here.
- We’ll add you to our allowlist.
- Add this block to your server’s
lemmy.hjson
config (for open federation):
federation: {
enabled: true
tls_enabled: true
# allowed_instances: lemmy.ml,other_instance.tld,... uncomment this to use an allowlist
}
- Type
!announcements@lemmy.ml
into your server’s search box, and subscribe to it to connect the two instances.
!community_name@instance.tld
into your server’s search box, and subscribing), then those posts will show up inAll
.We decided to make
Local
the default tho, because once this grows, there will likely be lots of spam inAll
just like mastodon. And of course you can set your default view to Subscribed, Local, or All in your user settings.All
by default, or just clickAll
on the front page to see federated posts.Are there any plans to make it possible to browse a remote instance’s community list without going to their site? That would make finding and subscribing to remote communities much more convenient IMO.
No, but you can open an issue.
I don’t think it’d be possible unfortunately, because there are only community and user actors, not instance actors.
Could this be solved with a special ‘root’ community with different semantics? Or is that too much of a hack?
I don’t see how that would work, any more than a “root” user. I don’t think mastodon has federated searching for things that live on other instances.
Is there a user preference to filter an entire instance from All?
deleted by creator
Local or subscribed, we don’t have blocking yet, of communities or users.