Conversation

Notices

1. Embed this notice
   nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Wednesday, 19-Mar-2025 16:12:00 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
   Pleroma adds groups. Millions clap and cheer, millions more break down into tears, Lain Soykaf gets the Nobel Peace Prize, all conflict around the world suddenly ceases.. Pleroma has just created world peace
   • Embed this notice
     of nothing (apropos@fsebugoutzone.org)'s status on Wednesday, 19-Mar-2025 22:02:12 JST of nothing

     in reply to
     @nyanide the fediverse is really IRC, but without channels.
     What did channels come with?
     1. chanops
     2. modes (and database of permissions)
     3. netsplit logic
     4. lots of administrative drama
     absent #1-#3 you get the problems that demanded them. With #1-#3 you get #4 which sucks. The intuitive way to add channels while minimizing #4 is to make them @ an instance. You don't have a fediverse-wide #root (except as twitter's crappy alternative to channels), but a #root@instance where the chanops and modes are managed by that instance, there's therefore no need for #3, and the clear authority simplifies the drama.
     
     But if you agree with that, then you don't need pleroma support for it anymore, but only a bot account rootchan@instance that people can follow (to join the channel), that can block people (to kick from the channel), that you can direct messages at (to talk to the channel), and which you'll receive spammy notifications from. An improvement over IRC is that conversations remain threadable with clear participants.
     
     Any single instance could implement that right now with no support, and if it gets popular and the details are worked out, *then* suggest minor UI improvements and in-server handling to not need the bot. But since any single instance could do this, and nobody has, it follows that people do not really care about channels. Therefore it's ALL OF YOUR FAULTS