Blocking someone should remove their replies from your posts, this is the type of safety features we need in the Fediverse!
-
-
@the_moep
I think you are ignoring the sense of space Mastodon gives for replies. It gives a sense that they are a part of a discussion within a digital space defined by the original post. The original poster should have some say over their sense of safety in the digital space of their own posts, and replies by blocked individuals should be disassociated from the post and not part of that digital space anymore. That's not destructive. It's not taking over another account or instance, it's taking control over your own account and the digital space Mastodon creates around it.@FWAaron @alterelefant @dansup
I don't agree with the "sense of space" for replies when it comes to moderation actions tbh. For me that's something which is up to moderators of your instance (and the instances you federate with), if those do not act in your best interest then you should find the ones that do...Also you already have something to say about your personal safety: You can mute/block people if you don't want to see them/give them the opportunity to easily link to your content, but if you don't want them to interact/see your content at all then the only solution is unfortunately to not post it publically at all. (Which is what people are already doing, both in posts and replies as well as instance-local timelines)
This is because any public post can be abused by malicious actors (either by linking to it or screenshotting it), this proposed addition to the block feature is not going to stop such abuse nor is it going to significantly slow it down.
-
-
@kelson
I disagree. Any given position in a comment tree currently is a perspective of the same tree (only posts that are neither a reply nor are a parent (both recursive) aren't displayed). If comments are hidden depending on the position, that would not just make for different perspectives of the same tree, but for different parallel ones.
@rimu @dansup -
@kelson
I disagree. Any given position in a comment tree currently is a perspective of the same tree (only posts that are neither a reply nor are a parent (both recursive) aren't displayed). If comments are hidden depending on the position, that would not just make for different perspectives of the same tree, but for different parallel ones.
@rimu @dansup -
@foxyoreos @Schafstelze @dansup the only way to federate it to other servers would be via publicly posting the ban, even if your full list isn't visible any server you've federated to would effectively have it, so it would be easy to scrape. I fully disagree, you don't own the fediverse, you don't own the thread you only started it, you can split and block further replies but you cannot kill a conversation down the chain from the one you started, it doesn't even need to necessarily involve you.
@raptor85 @foxyoreos @Schafstelze @dansup You don't have to be able to kill the whole conversation further down, but you should at least be able to stop your post from pointing to the next one down the line.
-
@kelson
I disagree. Any given position in a comment tree currently is a perspective of the same tree (only posts that are neither a reply nor are a parent (both recursive) aren't displayed). If comments are hidden depending on the position, that would not just make for different perspectives of the same tree, but for different parallel ones.
@rimu @dansup -
@raptor85 @foxyoreos @Schafstelze @dansup You don't have to be able to kill the whole conversation further down, but you should at least be able to stop your post from pointing to the next one down the line.
@kelson @raptor85 @Schafstelze @dansup Exactly. A lot of Mastodon/ActivityPub controls are like this. They're a little fuzzy, there are edge cases, but they mostly work. Just severing a link is fine.
-
-
-
@tnhd @rimu @dansup In my opinion, the benefit of enabling the average user to reject and stop pointing to outright abusive replies outweighs the drawback of enabling thin-skinned users to reject replies they merely don't like.
In the second case, at least the post still exists somewhere. And in the first, I'm not going to lose any sleep over whether detaching an actually abusive comment might as well be deleting it.
-
@gbargoud @alterelefant @dansup
The best way to handle this is:
* block account
* delete your post and repost it as a new post
* all references to the old post have gone@dnkrupinski @gbargoud @alterelefant @dansup IMO you shouldn't have to delete and rewrite your post in order to accomplish this.
-
@foxyoreos @Schafstelze @dansup the only way to federate it to other servers would be via publicly posting the ban, even if your full list isn't visible any server you've federated to would effectively have it, so it would be easy to scrape. I fully disagree, you don't own the fediverse, you don't own the thread you only started it, you can split and block further replies but you cannot kill a conversation down the chain from the one you started, it doesn't even need to necessarily involve you.
@raptor85 @foxyoreos @Schafstelze @dansup Right, you don't own the whole Fediverse. That also means you don't own the post you're replying to, and you shouldn't be able to dictate whether it continues to provide your post a platform.
-
Blocking someone should remove their replies from your posts, this is the type of safety features we need in the Fediverse!
@dansup Is'nt that the norm ?
-
J jwcph@helvede.net shared this topic
