New Communities
A place to post new communities all over Lemmy for discovery and promotion.
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:
or instance.com/c/community
FAQ:
Q: Why do I get a 404?
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: When I try to create a post, the circle just spins forever. Why is that?
A: 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.
view the rest of the comments
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?
Yes, it would best to use two links, that is why I said you should include the following format in the post, then said it gets a 404 sometimes, and to include one of the other formats too that you can use while searching, if it wasn't searched for already
Sorry, I must have missed that point in my first read through. I think we will see a lot of changes with Lemmy as development proceeds. It seems like that particular 404 is being generated in the Lemmy software rather than the webserver portion because that is not a standard 404 message. So instead of generating that message it could probably be fixed to kick off a "manual" search instead of generating an error. We will have to leave that to the Lemmy devs though.