The Discuss.Online instance uses lemmy federate for all communities. This shouldn't be necessary for anyone already on Discuss.Online.
Discover new communities
Welcome
Community discovery still needs some improvement. To help broadcast new communities locally or federated, this community will be a place to advertise your community or one you wish to share.
Tools
There are some tools to help discover new communities.
Rules
- Follow Lemmy code of conduct
- Only one community per post.
- Post must follow the formatting template below.
- No spamming of the same community.
Post formatting
Lemmy has specific requirements for searching for communities, posts, comments, etc. Because of this, you must format your post in an easy-to-copy-and-paste way for folks to search.
Post format
The formatting must include the following items in the format shown in a code block below.
Title
Title must include name followed by the community handle.
{community name}: {community handle}
Example:
cat pics: [[email protected]](/c/[email protected])
Fields
- Community name
- Description of the community or why you're sharing.
- Direct link to the community
- A local/relative link to the community.
- This is helpful to check if the community has already been federated with Discuss.online
Template
# {community name}
## Description
{describe what you like about it and what makes it unique}
## Links
- [Direct link](https://{domain.tld}/c/{community})
- [Local link](/c/{community}@{instance.tld})
Example:
# Discuss
## Description
Random chat topics. Great place to discover new things!
## Links
- [Direct link](https://discuss.online/c/discuss)
- [Local link](/c/[email protected])
I actually manually added some discuss.onlime communities. If they were already on there, it wouldn't let me add them. So apparently it's not working.
Communities on Lemmy Federate are updated every 24-48 hours. You can re-add existing communities to force immediate update. So it's a valid action.
Thanks! After I updated my configuration, I saw that the communities were queued for processing. I'll keep an eye on it.
Thanks! I'll look into it and see if I can find anything amiss!
It was linked with fediseer and was configured to only work with endorsed instances. I've disabled the fediseer option. I hope it works better now!