@wowaname @matrix @crunklord420 @nik @sjw > to show mastodon users why federated blocks were a privacy risk
I don't think this is a privacy issue for the person doing the blocking. What exactly is leaked? "This person doesn't wanna hear from you and does not want you to follow them any more, and the system has duly enforced this." I've never heard a real use-case. (If anyone's got one, I'm all ears, but the ones I have imagined are unconvincing.)
It *is* an issue for the person that has *been* blocked. Here is metadata about your account: two servers know it (and thus by extension, at least two admins plus anyone that gets unauthorized access to a server or a backup system that contains the DB dump), but you do not. Seriously, on what grounds should a user *not* be entitled to their own data?
> people on their instances had fun seeing who blocked them
Some people have fun with it, I personally think it's weird and passive-aggressive to not know who has blocked you, and I sure as hell don't want to waste time typing up a message at someone that won't see it and doesn't want to see it anyway. My use-case is that I don't want to waste time on that, since I'd rather talk to people that want to talk to me.
So we added it due to popular demand, but the more I think about it, the less sense it makes to hide this from the person that it targets.