Couldn't reach midwest.social until I manually entered URL
https://midwest.social/c/chicago
Both instances are on each other's list of linked instances but I couldn't get there from here via search. I had to manually add in /c/[email protected] in the address bar and subscribe from there before it started showing up in search. Is that normal...?
6 replies
It seems to work for me. It could be that it didn't work for you, because I just upgraded the instance to the latest Lemmy version. Maybe you tried to search in the very moment I did some backend work.
Let me know if it works for you now.
I am not subscribed to [email protected], but that one doesn't show up in community search.
Community content of "less popular" instances will show up in search once at least 1 person on this instance has subscribed to it.
I will add midwest.social to the seeder script on the server to have it periodically look up the most popular communities on there and subscribe to them automatically using a bot account, which has the same effect.
Result:
Oh I see, so that's by design... That list of instances is pretty long so I imagine an index of all their communities would be huge... and there's not separate "list of communities" and "posts within an instance" indices I assume? Is this something I should ask the lemmy devs about