974
The developer of Sync for Reddit is working on a Lemmy app
(www.reddit.com)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
I thought I was getting the hang of it until I couldn't find communities. I pasted the link into jerboa and it still can't find it.. I can see the community on a feddit directory but I can't find it in jerboa.
It may be a bug, I've been seeing some weird quirks in Jeroba myself, though I'll admit I'm still figuring it out.
I don't know about Jerboa, but this happens on the web too, and it's usually on more fringe / less popular communities. There's a workaround that works for me, I mostly heard about it from someone else here on Lemmy. It's not great user experience, but it works.
[!communityname@instance.server](/c/communityname@instance.server)
, all in lowercase. So, for example, if you're looking for the "kreisvegs" community on feddit.de, type[!kreisvegs@feddit.de](/c/kreisvegs@feddit.de)
on the search field;You may have to repeat step 4 onwards a couple times, sometimes.
My uneducated guess as to what's happening: the federated communities listing is probably cached on the instance, and by default it'll only look for communities cached on your instance. My guess is that federated communities only gets into the instance cache when members of the current instance have searched / subscribed to that community. Typing the fully qualified community name on the search field (which is the tip I got from someone else) apparently forces the search function to actually contact the external instance to look for the community, instead of looking in the cache, but that can take some time, hence why you should wait a few seconds on the 6th step. That guess could also explain the problem also happening on Jerboa, since the problem would be server-side.