|
|
|
|
|
by colinsane
1315 days ago
|
|
> cross-posting has been around for as long as there have been platforms. It just happens. there’s a range between “something i posted to my public newsletter/blog” and “encrypted signal chat message”. for most people, crossposting is OK in the former, but a clear norms violation in the latter. ultimately, this can only be enforced culturally — and yet most of us still expect that as viable: “it just happens” is the thinking of a selfish CEO who does something blatantly unethical and defends himself by claiming “but i didn’t technically break the law!” Mastodon is somewhere on this scale — and quite likely at least slightly closer to the chat end of that scale than twitter is, taken in whole. it also has features to signal what is appropriate (e.g. it’s more of a violation to cross-post something with a lock icon next to it than with an unlock icon than with a globe icon). but new users aren’t likely to have a strong understanding of this visibility setting, so it’s even more the case that a norm violation might be obvious to one section of the userbase while the (unacquainted) norm violator is completely unaware. yeah, defederating is a solution. in a similar sense that getting a restraining order is a solution to IRL disagreements. it’s more pleasant for everyone if you can reach shared norms and only deploy the stronger tools against those who actually mean you harm. |
|
Even for public posts? Which show up in the federated timeline for thousands of people you don't know, are visible to anyone who loads your profile, and can be shared by URL? To me that sounds very close to a blog post (no need to ask for permission to share) and not much like a direct message (definitely ask first).