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.
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.
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 instance
If 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”])