If you search Mastodon for “threads.net” you’ll see a bunch of people wondering why they can’t see President Biden’s account, unaware that they are on an instance that did a full suspend on the threads.net domain.
And people say Mastodon isn’t confusing 
The messaging on Mastodon needs to be a lot clearer.
“You cannot view this profile because your Mastodon server, example dot com, has suspended the example dot net domain.”
If there isn't an issue about this on Github, there should be.
@benx @jsit This was the closest I could find (though I didn't search particularly intensively) - https://github.com/mastodon/mastodon/issues/26271
@da5nsy @benx @jsit I looked at that issue and it can't be done. What it wants is it wants to see where the messages are not reaching. We don't know that. What we do know is what sites were blocking specifically.
Look, the thing is that activity pub is a push protocol. Each instance sends messages to all the instances that have people that are interested in its messages.
@jsit @benx @da5nsy I don't recall. Your instance may go out and pull the messages you're missing. However the originating site sends the messages to everyone who follows you, replies to your post, and posts you are mentioned in.
For instance let's say in this reply I remove @benx from the mentions at the top. This message would not go to their site.
And if either of the other people replied to my post it too would not go to their site.
That's my understanding anyway
@benx @da5nsy @jsit my understanding is the person is blocked instead of the site, the whole message is pushed, and then discarded by the blocked persons site. I don't think there's a handshake, so the originating site wouldn't know about the block.
Let's say that da5nsy blocks me, but isit doesn't. The message would still end up in social.coop messages, but it wouldn't be shown to da5nsy