Back

@ramsey Blocking a domain and an admin suspending a domain are two different things (though for a user I do believe they *should* be the same).

When blocking a domain, for some reason it's not historical, so even a blocked domain can still interact with your older posts for...some unknown reason. Because of that, they still show these accounts in searches.

Might want to generate an issue on Mastodon's github about this? Interesting discussion.

@shanie @ramsey he's an admin, but for users, it's functionally just a mute.

I've seen a user say "fuck kolektiva, just blocked the entire domain!"

And in the replies were kolektiva users asking why they could see and reply to the post.

@BeAware @shanie I'm asking from the viewpoint of a user, though. If I, as a user, block a domain, why do accounts from that domain show up in searches?

@ramsey @shanie oh...cause it's functionally just a mute and the search function doesn't "communicate" for lack of a better word, with your block/mute list.

@BeAware @shanie I understand. So, in order to avoid seeing all these junk accounts (Twitter cross-posters) in search results, I'd need to suspend the domains at the instance level?

@ramsey @shanie as far as I'm aware, yes, though it might not remove them from search until you clear their data or purge the domain from your instance.

I'm not exactly sure on how exactly to get them removed. I just know that if I search an account on my instance that I've defederated from, it doesn't show up.

Some trial and error with defederating and deleting their data might be required.

@ramsey @shanie

right. its unfortunate that there's no other way that I know of.

@BeAware @shanie So, I went through and defederated from all the birdsite crossposters except for bird.makeup. That appears to be the only one that works reliably anyway, and we have over 800 users who follow folks there. My searches look much cleaner.

@ramsey @shanie great! glad to hear it worked for those, at least!