@infodump@a.gup.pe @mastodonindians@a.gup.pe
The main feature missing from ActivityPub (Mastodon).
The THREAD should be a first-class OBJECT and the OP_USER of said thread should be the ACTOR with admin AUTHORITY of that THREAD object.
TL;DR ... the user who starts a top-level toot thread should have administrative power over that thread network-wide. All canononical links for that thread should point to the OP user account where signed revokes would be found to suppress or moderate network-wide. This lessens the importance of appealing to server administrators to moderate every troll, spam, or offensive post, allowing the OP user to clean up the thread as it will be seen by all users seeing the thread.
More detailed description
The goal is to allow the originating user of a thread to have maximal ban hammer power over all child toots in that thread for all views of the thread from the entire network. Signed control messages in the back end automatically sort it out for all compliant instances, bypassing administrators and relieving administrator workload. Moreover, this method also lessens the knee-jerk suppression based upon mere viewpoint, since if the thread OP wants to allow the comment to remain, the remaining users have the option to hide the thread already, or mute particular users.
The OP of a new post thread should have the power to moderate that thread regardless of where the followups come from. If I post a thread I should be able to remove comments from it network wide. This gets rid of the pretext for server-level censorship by politically motivated admins, allowing the OP and participants to decide which threads and comments they wish to tolerate or delete. This would also frustrate trolls and spammers, which is a good thing to be desired.
If some moron wants to post unnecessary profanity and baiting slurs in a thread that I started, I should be able to click a button to ban that moron from that thread and remove the moron's offending posts from that thread. Let the moron start his own thread about his vaunted superhuman superiority, which I won't ever have to see or deal with.
Instances should pull signed followups, deletes, edits, and bans from the server account of the OP account that posted the opening post for a thread. This would resolve a lot of issues and eliminate a lot of hassle for admins as well as a lot of motive for admins overusing the ban hammer. Every OP would have the ban hammer for threads started by OP.
Each instance should cryptographically sign OP key in thread responses, so that by default a signed revoke by OP key is proof of authority to revoke, causing compliant instances to reject the revoked object and not pull it in the first place, and to delete it in the second instance of discovery.
It is not enough to just mute a user. When some clown comes in to simply disrupt a thread the OP of the thread should have authority to resolve it. This is much better than filing a complaint with admins and waiting who knows how long for a response or resolution.
[#]ActivityPub #Fediverse #Mastodon #Moderation #Censorship #Threads
=> More informations about this toot | View the thread | More toots from lamp@neon.nightbulb.net
=> View infodump@a.gup.pe profile | View mastodonindians@a.gup.pe profile
=> View activitypub tag | View fediverse tag | View mastodon tag | View moderation tag | View censorship tag | View threads tag This content has been proxied by September (ba2dc).Proxy Information
text/gemini