Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
I guess so? there's no actual harm if nobody who is offended by the comment sees it. like all the horrible stuff on the web that we never browse to. I guess we could say those sites are problems too but that reality is not something people usually complain about, except maybe when some wanted to scare us off the web in the 90s. it was a trade-off for letting people create their own sites. this moderation approach lets us share a social network with people we don't agree with 100%.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc i get the idea, but i'm not sure if i like someone else to decide if i can see a reply or not.
-
@vkc Running my own instance to always keep my own data. What I don't like is that I can only follow users of other instances, but not a feed of another instance or a hashtag. Unless, I would join a relay but then get all those messages send to my instance which might overload it. So I just search for interesting people to follow on a lot of instances.
I have two separate accounts, one for following people and saying stuff, and one for following hashtags. In my case, both are on the same instance, but you could perhaps keep your account on your own instance for following people and saying stuff, and have an account on one of the big instances for following hashtags?
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc (Bookmarking this because it's the third time I've read the explanation for how the concealed harassment on the Fediverse happens, and on the previous two occasions I've forgotten the explanation.)
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc If your admin blocks "cesspool.domain", unless the maintainer of "cesspool.domain" forks mastodon and does some shenanigans, no user from that instance can follow any user from your instance and vice versa. They could go to your profile and take a screenshot of it or link to it if the post is public (vs "Quiet Public" or "Followers Only") but they can also do that if they aren't using Mastodon at all.
Truth Social is using an old, tweaked version of Mastodon but nobody federates with it.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
Instances also systematiclly forward toxicity reports to other instances.
-
@vkc i get the idea, but i'm not sure if i like someone else to decide if i can see a reply or not.
-
I have two separate accounts, one for following people and saying stuff, and one for following hashtags. In my case, both are on the same instance, but you could perhaps keep your account on your own instance for following people and saying stuff, and have an account on one of the big instances for following hashtags?
-
I guess so? there's no actual harm if nobody who is offended by the comment sees it. like all the horrible stuff on the web that we never browse to. I guess we could say those sites are problems too but that reality is not something people usually complain about, except maybe when some wanted to scare us off the web in the 90s. it was a trade-off for letting people create their own sites. this moderation approach lets us share a social network with people we don't agree with 100%.
"there's no actual harm if nobody who is offended by the comment sees it."
This is false. Have a think about what kinds of harm _could_ be enacted/supported via comments invisible to the target.
-
"there's no actual harm if nobody who is offended by the comment sees it."
This is false. Have a think about what kinds of harm _could_ be enacted/supported via comments invisible to the target.
I don't understand how it wouldn't be more effective to do this secretly. to share a link to the post in a private community of jerks. I haven't been harassed based on a post IRL but I have had people secretly share links to what I posted to mock me etc. using a reply might let you organize with more assholes who stumble on it, but would also allow others who don't block the assholes to alert the original poster and authorities.
unless I'm missing something.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc this is why community maintained blocklists are important (and I really wish we had a better way to share them between instances)
-
@vkc this is why community maintained blocklists are important (and I really wish we had a better way to share them between instances)
@vkc there’s always (unfortunately) going to be douchebaggery. you have ~23 million people in one big online room together. calling it out so people know who to block and defederate is a good first step, but the problem is that we actually need manageable ways to *do* those things cross-instance
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc Interesting, I didn't know. I wonder if I'm missing much from mastodon.social
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc Thank you for bringing this up and explaining how this is problematic.
Have you seen or come up with any good solutions?
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc Thank you for pointing this out.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc This is why I think blocking and user filtering should be done at a user level. Defederating a whole server because of some bad actors seems to me to be a sledgehammer to crack a wallnut.
-
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc Yeah, I hate that. Combine it with long-running BUGS that no one seems to even bother considering as such, and all in all #mastodon is a pretty shitty app.
"cesspool.domain" pff. It's called "people I disagree with", mom ; Between reasonable and cesspool I'd chose cesspool anytime. Oh yeah, that, too: The #fediverse is simply plain BORING.
> If your instance blocked "cesspool.domain", you won't see that reply
Yeah. Hate-that-shite ; The *opposite* of dialogue.
Have a nice safe 🥱 day.
-
@vkc there's a
seperate problem where you might not see a reply even if it has not been blocked; the latest issue of the mastodon software looks to fix that one.@fishidwardrobe @vkc that version that fixes that is already deployed on most mastodon instances atm
-
@gabe @vkc this is a limitation in Mastodon. Other federated software (famously MissKey, IIRC) does allow that. Hopefully this will be implemented in Mastodon too.
See also
https://github.com/mastodon/mastodon/issues/6942
https://github.com/mastodon/mastodon/issues/21327
https://github.com/mastodon/mastodon/issues/22637 -
Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
Let's say you're reading a post from "reasonable.domain". And someone from "cesspool.domain" replies to it. If your instance blocked "cesspool.domain", you won't see that reply.
This effect minimizes the appearance of harm. It can be a blessing, but it also means you won't always see the problems inherent on these platforms.
@vkc nice point. and clearly sorry to learn about your harassment.
It needs to be fought online *and* in real life...
