It really not. What if just do not want to see their post, for example because low quality or topic i not like? Block is a post/comment filter for feed, nothing more.
Maybe named wrong if you expect it to be more than it is. But functionality very useful.
Maybe should be able to block post/comment seperate, sound like good idea.
But block would mean activate a feed filter for someone else. Could abuse remote filter activate some way, probably.
It probably also filter on instance side, so if instance of blocked person ignore request to activate block filter, block is useless. And block actually not do anything might confuse people or accuse dev of malice.
It really not. What if just do not want to see their post, for example because low quality or topic i not like? Block is a post/comment filter for feed, nothing more.
Maybe named wrong if you expect it to be more than it is. But functionality very useful.
Maybe should be able to block post/comment seperate, sound like good idea.
I would argue that there should be a block feature and also a mute feature. What we currently call “block” is actually just a mute.
Mute really is better name.
But block would mean activate a feed filter for someone else. Could abuse remote filter activate some way, probably.
It probably also filter on instance side, so if instance of blocked person ignore request to activate block filter, block is useless. And block actually not do anything might confuse people or accuse dev of malice.
Mastodon manages to do it on ActivityPub