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 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.
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’ve been running into this issue as well(also on jerboa). It seemed as though I needed to create a new account attached to the instance I was linking to in order to subscribe to the community. I don’t want to have to juggle between 3 or 4 accounts to browse the communities I’m interested
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@instanceDoes 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
I tried doing that with a previously unsearched/unsubscribed community as a test on my own instance, and I got a
404: couldnt_find_communityerror 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.
@Akhuyan, I just wanted to let you know that you’re doing a great job.
Thank you for saying that!
I have had the circle that spins forever both when creating a post and when replying to a post. I found that if I close my browser tab and go back to where I was, the post/comment is there.
Q: Is it better to create my community on a large general Lemmy instance, a topical Lemmy instance, or create my own Lemmy instance?
A: It is up to you, but there are a few things to consider. General instances will likely help early discoverability, and your main account is likely already on one. However, your community will encounter risks of admin change and others defederating with the general instance for reasons unrelated to your community. If the account you want to be your main Lemmy home is on another instance, you must create an alt account on the general instance to create the community.
Self-hosting an instance will let you be in control. You’ll have fewer worries about your community not being found due to defederation or the instance admins shutting it down over reasons unrelated to your community. However, you’ll have to rely on word of mouth, communities like this, and the community search tools like Lemmy Explorer to get people there.
Topical instances might be a good middle ground if you trust the instance admins. As the local feed will have related topics, you’ll likely be a positive contributor to the local instance feed and find a lot of shared interests with others on that instance. Topical instances will probably only be defederated by instances you wouldn’t want to federate with already. If the account you want to be your main Lemmy home is on another instance, you’ll need to create an alt account on the topical instance to create the community.
Edits: network issues, reworded
deleted by creator
My spinning issue was resolved by not selecting a language when posting. Keeping it as Select Language allowed me to post.
