Conversation

Notices

1. Embed this notice
   Tim Chambers (tchambers@indieweb.social)'s status on Saturday, 16-Dec-2023 01:28:27 JST Tim Chambers

   • L. Rhodes

   @lrhodes At my sever being thinking about this deeply. Main point for us has been to up our moderation staff and prepare for more server load. Both good problems to have though.

   And to be clearer: by far most of the server load from Threads Federating will be on Threads servers. We'd only see Threads users or content OUR users actively follow, or boost, or that show up searches our users actively look for.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Saturday, 16-Dec-2023 06:13:14 JST Tim Chambers

     in reply to

     • L. Rhodes
     • Clifford Adams

     @wikicliff @lrhodes

     A good point: and know Mastodon folks are actively working on reply solutions. Frankly Threads itself now has far better reply moderation tools than we do.

   • Embed this notice
     Clifford Adams (wikicliff@fosstodon.org)'s status on Saturday, 16-Dec-2023 06:13:15 JST Clifford Adams

     in reply to

     • L. Rhodes

     @tchambers @lrhodes
     "only see [content] actively [followed/boosted]":

     This is missing something: people see bad *replies* not chosen by the follower or booster.

     Even an innocent cat picture can get nasty replies. Normal users will read every reply they are mentioned in even if downranked.

     If reply controls are implemented in time and widely available/used this may be less of a problem, although at the cost of friendly stranger replies.
     1/x

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Saturday, 16-Dec-2023 07:41:19 JST Tim Chambers

     in reply to

     • L. Rhodes
     • Clifford Adams

     @wikicliff @lrhodes Fully agree. Threads now has a “hide comment” feature we should steal. The comment is gone to everyone but the original poster who never knows you ghosted it.

   • Embed this notice
     Clifford Adams (wikicliff@fosstodon.org)'s status on Saturday, 16-Dec-2023 07:41:20 JST Clifford Adams

     in reply to

     • L. Rhodes

     @tchambers @lrhodes
     In addition to reply controls, I'd like to add an ability for the original thread poster to "cut/prune" bad replies--just removing them from the thread tree. They would not be deleted (that is a decision for a moderator), just not attached to the original thread.

     Technically this would probably be a new message sent out informing clients that message "id2" should no longer be threaded under message "id1".

     Thanks for an interesting discussion!
     2/2

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Sunday, 17-Dec-2023 02:35:30 JST Tim Chambers

     in reply to

     • L. Rhodes
     • small circle 🕊 in calmness
     • Clifford Adams

     @smallcircles @wikicliff @lrhodes

     Yes: the work I referenced included #FEP's on this!

   • Embed this notice
     small circle 🕊 in calmness (smallcircles@social.coop)'s status on Sunday, 17-Dec-2023 02:35:32 JST small circle 🕊 in calmness

     in reply to

     • L. Rhodes
     • Clifford Adams

     @tchambers @wikicliff @lrhodes

     > Mastodon folks are actively working on reply solutions

     Hopefully work on #FEP's too. The time when #Mastodon could walk the follow-the-leader happy path is coming to an end.

     The entire ecosystem must level up

     “Any decentralized [ecosystem] requires a centralized substrate, and the more decentralized the approach is the more important it is that you can count on the underlying system.”

     — Byrne Hobart.

     https://www.thediff.co/archive/the-promise-and-paradox-of-decentralization/