Support / questions about Lemmy.
You need to use the search function in the UI here https://lemmy.ca/search, not type the URL directly in your browser.
I just this for you and now the link works properly.
Just have in mind the first time you search for a community it might take a few seconds and a few refreshes to actually see it.
Thank you! This worked for me ๐
can you try searching for http://lemmy.ml/c/apple in the search field? Maybe your server just hasn't looked this community up yet. I don't think visiting http://lemmy.ca/c/[email protected] triggers this.
Yup that was indeed the case. Looks like the server didn't know about that community. Doing a search worked and I've successfully subscribed to it
awesome!
Communities are only pulled onto your instance the first time somebody subscribes to it. If nobody on lemmy.ca has subscribed yet, do this
Yup, works perfectly now. Thank you
Iโve been having the same issue with http://lemmy.world/c/hackintosh - and still having it with http://lemmy.ml/c/apple - guess Iโll just keep trying.
check out this post I made yesterday where I have a same/similar problem https://lemmy.one/post/19823
Thank you, searching for the full community URL "https://lemmy.ml/c/apple" here "https://lemmy.ca/search" helped the server discover the community and I was able to subscribe
Lemmy.ml is overloaded and known for having this issue. Also, even if it says "pending" you might already be subscribed. I just saw this in my subscribed feed even though my subscription to this sub is still pending.
I feel like there needs to be a pinned guide at the top of this instance explaining all of this stuff to new users.
If you're the first person on your instance to subscribe to a Community on a different instance, you need to make your instance discover the other community.
You can paste the URL or [email protected] in the search field on lemmy.ca, then you should be able to find it on lemmy.ca -> Communities
But looks it doesn't always work for all communities. I just tried it on reddthat.com. It worked for [email protected], [email protected] and [email protected], but not for [email protected]