@TJ @vodamark @taylorlorenz Yes. Twitter’s “Only People Mentioned Can Reply”/“Only Followers Can Reply” was:
1: developed to mitigate noise/spam/dog piling/harassment/protests without dedicating policy (& human labour for actioning) to AUP violations;
2: needed a central technological access control system to enforce it.
If it were written into the specification … it might not be honored by some instances, but that could be a defederation condition.
@PennyOaken @TJ @vodamark @taylorlorenz
I love the idea of defederation conditions that are "fast"-- ie if you're not respecting X then you're clearly not respecting the basic tenets of the platform.
It makes test suites more important for alt implementations but it also solves renegade bots and more
@huxley @TJ @vodamark @taylorlorenz my instance and/or client definitely has “Mute this conversation”.
One of the use cases for restricting replies is to counter & prevent misinformation from piggybacking on a conversation or announcement with a wide distribution / reach, so in such a case “Mute this …” would be insufficient.
@PennyOaken @TJ @vodamark @taylorlorenz
Couldn't the instance you are on filter replies that are not from people you mentioned, or followed ?
At least then the OP doesn't have to filter through the junk themselves.
@PennyOaken @TJ @vodamark @taylorlorenz
> 2: needed a central technological access control system to enforce it.
Not really. We already can kinda have it in some way:
a) the canonical view of the thread is served by your instance, so it can refuse to publish some replies there (using whatever internal logic it wishes to use),
b) when a reply is sent to the OP's followers, if the OP's followers list is not public, it's the OP's instance that does that forwarding (and can choose to refuse to do so based on any internal logic it uses).
If OP's instance is Mastodon/Pleroma/Akkoma and blocks (suspends) the domain of the replier, both of these things will happen. I don't know which kinds of other blocks (incl. in other instance software) will currently cause which subset of them to happen, but would hope that OP blocking the replier would also cause both to happen.
This obviously doesn't prevent the replier from sending that message to e.g. people explicitly mentioned. Alas, they could send such a message as a straight-up new message instead of a reply, and no reply-blocking would help with that (point (a) above already deals with visibility of that as a reply when viewing the OP's post).
@PennyOaken @TJ @vodamark @taylorlorenz
Mastodon is good like it is. If you don't like to be questioned, answered, etc, please close your accounts or block everybody.
Mastodon has the tools so you don't have to depend if a dictator to tell what to say, what to think, etc.
There were versions of mastodon that did that. They were defederated.
If mastodon does not provide the features you like, it is better to migrate to another networks.
@PennyOaken @TJ @vodamark @taylorlorenz
Mastodon has far more moderators than the birdsite.
3 o 4 moderators average by instance, times 3000. Besides everyone have powerful moderation tools.
Everybody can block an user or entire instances and they are just gone.
@pthenq1 @TJ @vodamark @taylorlorenz
Everything open will be exploited for fun, politics, and profit;
In an active crisis there is no real-time knowledge, only real-time information.
Mastodon should be about knowledge. As more people join, its exploitability for (mis)information scales exponentially, and infrastructure which addresses that should be planned for.
Thanks for coming to my ModX Talk
@PennyOaken @TJ @vodamark @taylorlorenz
Perhaps. There're tools to avoid that already in place. We were being attacked for all kind of trolls. They could not yet solve mastodon.
We will see. Even in your scenario it can be easily muted.
@PennyOaken @TJ @vodamark @taylorlorenz
For example, nobody can search in mastodon. And tags can be muted.
It is open, but no uncontrolled.