I agree that blocking is important. I just think that the framing here is very mastodon centric, and not really a thing that makes sense given how BlueSky works

I agree that blocking is important. I just think that the framing here is very mastodon centric, and not really a thing that makes sense given how BlueSky works. For example, due to having true account portability, if you tried to block a particular instance, they could just move to another one to evade that block. You need to block the account to prevent this. If there’s an instance that hands out usernames as a subdomain, you could write a moderation service that takes that into account, but then they could transition to their own username, stay on the same PDS, and that would no longer work. The more BlueSky native way would be to run a moderation service that tags accounts, and then a blocklist that bans accounts that get the tag. You’d then want to tag accounts that post from that PDS, and now, even if they move, they’re still blocked. That is to say, “you can’t really do that” doesn’t mean that that isn’t important or impossible, just that different protocols require different means of implementing requirements.