Conversation

Notices

1. Embed this notice
   Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Thursday, 06-Apr-2023 22:19:15 JST Thomas 🔭🕹️

   in reply to

   • David Gerard
   • Glitch

   @glitch @davidgerard If it’s approximate that’s enough. Unwanted replies won’t get to you and most people (who use software that respects reply limitations) won’t see them either. Possibly could automatically limit or defederate from instances where it’s not respected.

   • Embed this notice
     Glitch (glitch@pl.glitch.pm)'s status on Thursday, 06-Apr-2023 22:19:17 JST Glitch

     in reply to

     • David Gerard
     • Glitch
     @davidgerard @thomasfuchs The only legitimately impossible thing is reply restrictions. Those just... don't work under the Fedi model.
     
     You can kinda approximate it by silently discarding stuff on your home instance, but replies get sent to everyone that follows a person so it'd defeat the point.
     
     Basically:
     - Alice on instance A is followed by Bob on Instance B and Carol on Instance C. Bob also follows Carol.
     - Alice makes a status with the intent of preventing anyone on Instance C from replying (but not from showing up on Instance C).
     - C's instance doesn't bother with respecting reply restrictions for whatever reason, so Carol responds to Alice's post since she's a recipient to Alice's posts.
     - A's instance rejects the reply (as it should) but because Carol is also followed by Bob, B's instance will still ingest the reply, defeating the purpose of the reply restriction.
     
     This goes for a lot of the fediverse's external moderation tools to be clear. They don't work nearly as cleanly as you expect them to, they just work "approximately". You *need* to keep in mind that every external instance is a possible hostile actor who can mess with your privacy and message settings on your statuses in any way they want to.
   • Embed this notice
     Glitch (glitch@pl.glitch.pm)'s status on Thursday, 06-Apr-2023 22:19:18 JST Glitch

     in reply to

     • David Gerard
     • Glitch
     @davidgerard @thomasfuchs (really the longer I look at Mastodon, the more comparable it's development starts to become to TwinAphex' maintenance of RetroArch... that is really not a good thing.)
   • Embed this notice
     Glitch (glitch@pl.glitch.pm)'s status on Thursday, 06-Apr-2023 22:19:19 JST Glitch

     • David Gerard

     @davidgerard @thomasfuchs Want to point that this goes for almost every single major feature where you go “wait why isn’t that possible”.

     For another example, it has been degrading Markdown to plaintext since forever and only after literally almost a decade of complaining (not joking, Markdown degrading has been an issue since 2016) is Gargron finally adding a subset of Markdown (which is all that was asked). Yet another one is configurable character count.

     The reason people go “use something else” is because most people know that Gargron is obstinate about certain features. Its just not worth putting up with him when it’s already fixed in forks and work it out without needing to deal with him. And frankly it’s not just him. Gargron has a defense squad of orbiters around him who basically kiss the earth he walks on and will get really upset if you don’t sugarcoat every complaint.