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/chicago@midwest.social in the address bar and subscribe from there before it started showing up in search. Is that normal...?

1 points · 6 comments · view on lemmy.world

6 Comments

NettoHikari@social.fossware.space · 0 pts · 3y (4 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.

yaomtc@social.fossware.space · 1 pts · 3y (3 replies)

I am not subscribed to Tulsa@midwest.social, but that one doesn't show up in community search.

NettoHikari@social.fossware.space · 3 pts · 3y (2 replies)

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.

NettoHikari@social.fossware.space · 3 pts · 3y

Result:

yaomtc@social.fossware.space · 2 pts · 3y

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