You literally can’t do it. If you try, you just get an error message. Pretty much anything from hexbear.net is unblockable. Which is really unfortunately, because it is one of the worst instances out there.
Can you describe the steps you’re going through to attempt to block it and what you observe? For instance, if I go to https://fedia.io/d/hexbear.net and click block on the side, it instantly appears to work without any errors. I tried from other mbin instances as well and didn’t see any errors.
You can’t block any user or community. It just gives you a 500 error.
Thanks, was able to get the logs for the error happening with some help. Seems to be related to their “allowlist” changes to lemmy (at least that’s the error being thrown back). I’ll try to track down in the code, as I believe I mentioned before I believe it sends a request to unfollow to remotes even when you aren’t following, and make a patch soon™. (For jerry, this is an mbin bug, so feel free to move this to the mdev mag if you want or it can hang out here but isn’t specific to your instance)
As an update, this should be fixed as of this PR
I was able to verify that I couldn’t block before, and could after the change So it should get into the next tagged release version (which will likely be 1.5.0) and eventually be working on this instanceIf you have ublock origin adding the following to the filter list should help.
fedia.io##article.entry:has(aside.meta > a.magazine-inline[href$=“@hexbear.net”])
Blocking instances on kbin / mbin does not work though. You will still see the communities threads & users (and getting to that page in the first place is a hassle too since there’s no link to it).
Yeah, same with Kbin. It’s been an issue for a while now.
Pretty much since forever.
