I just blocked the whole instance as soon as the option was implemented. There were few good posts/comunities from it, but overall better to block it whole.
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’m actually getting pissed, I have hexbear.net and test.hexbear.net both instance blocked in Voyager but can still see these cretins comments. I could tag them all but that would take forever.
Edit: Fuck it, just blocking them when I see them.
Instance blocking blocks the comms, not the users. You will have to block every user you see if you’re reflexively anti-Hexbear, or move to an instance defederated from them entirely.
I just blocked the whole instance as soon as the option was implemented. There were few good posts/comunities from it, but overall better to block it whole.
Somehow I can’t block it using Voyager, the only instance appearing is
test.hexbear.net. Any idea why?SJW blocks them already.
Really? Last time they federated with us they’re the ones who ended up defederating and I thought that was the end of it
They’re mutally defederating.
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.
SJW? Social Justice Warrior? Is that an instance?
sh.itjust.works shit just works
That should be SIW…
@sh.itjust.works
I’m actually getting pissed, I have hexbear.net and test.hexbear.net both instance blocked in Voyager but can still see these cretins comments. I could tag them all but that would take forever.
Edit: Fuck it, just blocking them when I see them.
Instance blocking blocks the comms, not the users. You will have to block every user you see if you’re reflexively anti-Hexbear, or move to an instance defederated from them entirely.
That’s so fucking lame. I didn’t know how good I had it this whole time. But I am absolutely petty enough to block every user from there.
I believe you.
I’d recommend you go to an instance that blocks hex, like lemmy.ca or sopuli.xyz.
I’m not giving up my account because of Nazis. I’ll block every one of them if I have to.