@dansup @pixelfed

Yeah, “block” should be both ways. If it is only stopping you from seeing stuff, I think it should be called “mute”, which would fit with standard terms and people’s expectations.

@dansup I said "no" mostly because in a federated context it's going to be impossible to enforce this. If I'm missing a way that would enforce this, I might change my vote to "yes"

@dansup@mastodon.social @pixelfed@mastodon.social voted unsure because yes in theory it’s be best, but how can you enforce it?

@dansup @pixelfed in the end, it doesn't have to work in 100% of the cases. The blocked user can always create a new account to circumvent the block, but implementing blocks only one way keeps reminding the blocked user of the fact with every post.

@dansup @pixelfed well i'd say it would be nice if the post didn't appear in the timeline.

but ultimately, the person blocked can just sign off and see the post that way anyway

@dansup @pixelfed ideally yeah...

In the current Fediverse, no, waste of effort to attempt to implement it.

If someone wanted to view your posts they could if its a public profile, by logging out, or making another account etc, or just using RSS.

@dansup @pixelfed Feels to me that posting public content and then wanting control over who can see it is mutually exclusive. If one would wish to communicate in a closed manner then perhaps @pixelfed, maybe the Fediverse in general, is the wrong tool for the job.

@dansup @pixelfed If they were able to see your content that wouldn’t be a block, that would be more like muting them

@dansup @pixelfed
If I just want to tune someone out, I can mute them. If I block them, they should not be able to see me either.