Rules
The rules may be more established as time goes on, but it’s important to have a foundation to work on.
1. Follow the rules of Lemmy.world - These rules are the same as Mastodon.world’s rules, which can be found here.
2. Include a community title and description in your post title. - A following example of this would be New Communities - A place to post new communities all over Lemmy for discovery and promotion.
3. Follow the formatting. - The formatting as included below is important for people getting universal links across Lemmy as easily as possible.
Formatting
Please include this following format in your post:
[link text](/c/community@instance.com)
This provides a link that should work across instances, but in some cases it won’t
You should also include either:
FAQ:
Q: Why do I get a community not found message?
A: At least one user in an instance needs to search for a community before it gets fetched. Searching for the community will bring it into the instance and it will fetch a few of the most recent posts without comments. If a user is subscribed to a community, then all of the future posts and interactions are now in-sync.
*Q: Why isn’t the link working on kbin.social?"
A: This is a community for Lemmy, there is a universal link for Lemmy, but when this universal link works on kbin. It turns out like the below.
https://kbin.social/c/newcommunities@lemmy.world/
Simply replace the c with an m for kbin.social like shown below.
https://kbin.social/m/newcommunities@lemmy.world/
*Q: When I try to create a post, the circle just spins forever. Why is that? *
A: (This may be removed soon as it is seems to be happening less often now.) This is a current known issue with large communities. Sometimes it does get posted, but just continues spinning, but sometimes it doesn’t get posted and continues spinning. If it doesn’t actually get posted, the best thing to do is try later. However, only some people seem to be having this problem at the moment.
Cross-Posting
On Lemmy you can use the the built in cross post function to link viewers of one post to another. This lets users quickly see what people in other communities are saying and also has the potential to expose someone to something new. For community owners this is a great way to go about seeding discussion in new communities.
Example:
Thanks to this post and creator for this tip!
Is there a place for us to request new communities?
I tried doing that with a previously unsearched/unsubscribed community as a test on my own instance, and I got a
404: couldnt_find_community
error when clicking the link. As you stated, it seems like in most cases that special link will not work unless someone has previously manually searched for the same community in your instance.I think I’d rather link directly to the instance for the community than get a 404 error. For most people, getting the 404 will just deter them from proceeding further.
Perhaps it would be best to include both links in a post?
@Akhuyan, I just wanted to let you know that you’re doing a great job.
Thank you for saying that!
At least one user in an instance needs to search for a community before it gets fetched.
Look, I kept doing that on “!lycorisrecoil@lemmy.ml” and link to the community still does not appear on my search results while am on .world. I also tried to click the links on their post in this community and it still won’t let me interact as .world and kept appearing as .ml and “not logged in”.
Is this an ongoing bug between instances’ interactions?
I just tried to click on a couple links formatted in various ways from a “jerboa for lemmy” app and it redirected to a browser (where I am not logged in).
Is there a format friendly to the app, or is there a app config that needs to be updated?
I have never used the Jerboa app so take this all with a grain of salt, since it may be different than the website. The link with the
[link text](/c/community@instance.com)
should only work if the community is already linked with your instance, the two other formats can be put in the search bar, and after the instance fetches it, it should show up, but not sure how this all works on the app version though[link text](/c/community@instance.com)
Crashes jerboa
[!community@instance](instance/c/community)
Opens the community in a new browser where you are not logged in
!community@instance
Does not work, thinks it is an email address and prompts to open in your email app
The problem is jerboa, I believe it is being looked into by the devs