Do you mean blocking a domain? So navigating to /d/domain_to_block? If you do: that blocks all posts that have a url linking to domain_to_block. Since comments do not link to anything they will not be blocked by this. If you want a feature like this, please consider making an issue over on github in the mbin repo
It definitely does not block threads from those instances showing up. For example I have lemmy.ml blocked that way and I still get the occasional lemmy.ml threads pop up and have to manually block all the different communities on that instance.
That makes no sense to me. Imagine blocking users would work the same way and it would just remove links to their profile, but not the stuff the account posts.
Think of it this way: there is currently no way to block an instance from a users perspective, there simple isn't (and yes we should add one). What blocking a domain is for: I hate everything the guardian posts, I don't want to see anything talking articles by the guardian.
To get to another instance there is the "Magazines" link at the top of the page, or just go directly to the one you want such as https://fedia.io/m/anarchychess@sopuli.xyz
To create a new one is under that '+' icon at the top of the page. Looks easy but I haven't tried it yet.
I'm not sure what goes wrong, assuming kbin.social didn't block fedia, then I suspect some kind of issue at fedia.io. I believe we need to debug this issue on the server-side. Hopefully @jerry can have a look at his logs when trying to execute the search query above and maybe find the root-cause that way.
ok - just looked through logs and I am not seeing anything that looks related to this issue. There are a good number of error 500's coming from kbin.social, but none appear to be around the time of these posts, nor associated with the referenced magazine.
Fedia Discussions
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.