When I backswipe to go back to the search page, and click on Random Community again, I get a yellow error dialog saying "Failed to find random community"
No choice but to go back to the search page.
Random Community again returns me to 100yearsago
Back and Random Community gives me the yellow "Failed to find random community" dialog.
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?
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:
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 can see the error eventually by clicking search and random a bunch, even without clicking or swiping back. Maybe the random functionality is pulling up a community with bad data or we’re getting rate limited. Not sure!
If you are on a random community, you can also ‘pull to refresh’ (pull down from the top of the list), which will load a new random community. Does that work properly?