Friendly reminder that Mastodon, et al is federated, which means you almost certainly won't see every reply on a thread.
-
@vkc I only use open source, Mastodon and Loops. No need to know what’s said on bird site or bs.
@Beachbum this happens on Mastodon. It's what happens between instances as a result of federation/defederation.
-
-
@vkc I feel like this exact problem has been brought up with the issue of racism being made invisible, creating the impression among people on other servers that it wasn't existent on the fediverse.
It's as if gaslighting was built into the system by accident. That is; there's somethings some people can see but others can't.
-
Yes. Another inherent problem is replies may reach you very late. When a discussion is going on, not all participants may see replies quickly, or while the discussion is ongoing. So the friendly reminder includes hints for patience too
-
@cyberwitch @vkc Yeah, I could imagine if there are heaps it could be messy to navigate though.
Maybe when you expand a post, under it could say something like "x replies from blocked instances" which would increase the transparency. Maybe a button to temporarily unhide them too.
-
You can at least sometimes work around this by clicking on the three dots and choosing "Open original page", at least on the web interface.
@cptbutton @vkc yep
-
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 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.
-
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
