Voyager

I can see this being very taxing on an instance's network resources, maintaining and sending the complete list of communities that it has access to every time a request like this is started.

How would that even work?

Any given instance only has records of the /c's that its users have joined, and there are likely plenty of /c's that its users have not joined.

What if some instances have disappeared, along with their /c's? There are some zombie /c's out there because of this, and those could really use some cleanup because their content is still in the caches of many instances.

What about de-federation? What happens to de-federated /c's?

Interesting, I didn't know you could do that!

But it doesn't really work.

It seems to cycle between "Failed to find random community", !100yearsago@sh.itjust.works , and !categoryiii@lemmy.world - which is a /c that I subscribe to already

I tried on my iOS device, v 2.9.1 and it's behaving similarly to what I describe in my reply to @pro_user@lemm.ee who told me about pulling down to refresh:

It seems to cycle between "Failed to find random community", !100yearsago@sh.itjust.works , and !categoryiii@lemmy.world - which is a /c that I subscribe to already

but in iOS v 2.9.1 it adds !3dprinting@lemmy.world , and wowthisnsfwsubexists@zerobytes.monster - which returns a "nothing to see here" message, and some Korean NSFW /c that has never come up again after coming up twice.

I am using Android v 2.9.1

🎵 "Today's random number... 3 bits" 🎵