Example: I have a community c/[email protected]
Searching for these on other instances like beehaw.org or lemmy.one:
!lanadelrey@lemmy.worldhttps://lemmy.world/c/lanadelreyhttps://lemmy.world/c/lanadelrey@lemmy.worldc/[email protected]lanadelrey
Gives No results. even after waiting several minutes and trying multiple times
I had this problem with [email protected] too, but now it seems to work as expected! So this begs the question: is there a delay before the communities can be discovered? How long do you have to wait in general?
This is how it works from what ive gathered:
First search for it using [email protected] then go to the URL manually: https://currentinstance.domain/c/[email protected]
Then subscribe from there. Needs to be done if no one has already done so for that particular community between those 2 instances. Definitely needs reworking to be more user-friendly.
For me, searching using the remote URL works better.
Example URL: https://beehaw.org/c/technology
Same :) And sometimes if not found try again or click ‘next’
Oh hey stux! Nice to see you here!
Can you please try with that sub? Of course, you can un-subscribe right after. Just as a sanity check, because for me it does not appear.
Thank you,
Had to use my Lemmy.World account to do it for your instance but check now and you should see one subscriber and it should now be visible in search.
I have that issue too through the Jerboa app and also on mobile browsers. It just doesn’t work on my phone at all right now.
However it does work on a desktop browser for some reason. I use chrome on both laptop and phone, so it’s kind of weird, but I managed to find and add a lot communities by using the laptop.
i have had slow access trying to get stuff from beehaw.org but I have no issues with lemmy.world.
this may have to do with various deployment choices these teams have made. Location in the world still matters even if using something like akami. as the network gets more instances sharing content the gaps will close.
