I can access hexbear communities, at https://sh.itjust.works/instances only test.hexbear.net is listed which leads to 502 anyway. Am I doing something wrong?
It makes sense, all the posts I find from hexbear are a couple of months old. It is a bit annoying, because when I hit explore in Voyager and sort by size, thalf of the communities are from hexbear… Maybe @TheDude@sh.itjust.works has an idea why it behaves like this?
Hexbear used to be federated with sh.itjust.works. if you defederate, the old posts still continue to exist, hence the communities also still continuing to show.
I can access hexbear communities, at https://sh.itjust.works/instances only
test.hexbear.netis listed which leads to 502 anyway. Am I doing something wrong?Probably an issue on sh.itjust.works’s end, though Hex blocks it so they won’t see anything on your end even if you do get in.
If you want to see what it’s about, just visit hexbear.net directly.
It makes sense, all the posts I find from hexbear are a couple of months old. It is a bit annoying, because when I hit explore in Voyager and sort by size, thalf of the communities are from hexbear… Maybe @TheDude@sh.itjust.works has an idea why it behaves like this?
Hexbear used to be federated with sh.itjust.works. if you defederate, the old posts still continue to exist, hence the communities also still continuing to show.
I tried removing a bunch of the old hexbear communities. Did that help at all?
Also sorting communities by total subscribers is a bad system. It’s more useful to sort by monthly active users imo.
You can use lemmyverse to sort by active users.
https://lemmyverse.net/communities?order=active_month
Check the blocked tab. Also, when servers defed, old posts and comms stay behind.