Conversation

Notices

1.  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 01:06:37 JST 
   Apparently pisskey doesn't have to/cc fields in its "reaction" (botched Like) activities which makes preemptive filtering impossible. Might as well add a toggle to reject them all instead.
   • тняэдт™ (threat@ryona.agency)'s status on Friday, 26-Jul-2024 01:08:58 JST тняэдт™

     in reply to

     @mint it's set under a boolean feature flag of balls = false

      likes this.
   •  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 01:09:33 JST 

     in reply to

     • тняэдт™
     @threat Pee is stored in the balls, so yes.
     https://gitgud.io/ryonagency/pleroma/-/commit/bb19a0a0e028f3995356c06b71cda01dfbfc045a
   • тняэдт™ (threat@ryona.agency)'s status on Friday, 26-Jul-2024 01:11:33 JST тняэдт™

     in reply to

     @mint impeccable opt naming handle_pisskey_reacts. keep up the good work

      likes this.
   •  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 01:37:45 JST 

     in reply to

     • Angry Sun
     @sun The goal is to completely sever s2s communication with pedophiles (currently 66 domains and 15 actors not covered by those domains, plus 4 more complicit actors for whom I don't also remove media yet) beyond what is necessary to not break thread contexts and to be able to send a woodchipper or some other repellent. This means no likes/repeats/reacts and follows both in and out.
     The former could easily be filtered by checking whether the `to` field contains the actor meeting criteria; however, Pleroma's pipeline is faulty in a way that it fetches the referenced object before MRF filtering activity referencing it. This can be solved with a single line that puts MRF filter earlier in handle_incoming.
     Overall it was pretty effective, but pisskey's reacts don't contain any `to` fields in their first form at all, meaning there's simply no way to filter them without fetching the object. So I just decided to kilt them in entirety.
   • Angry Sun (sun@shitposter.world)'s status on Friday, 26-Jul-2024 01:37:46 JST Angry Sun

     in reply to
     @mint every second, new incompatible messages/implementations join the network, this is totally sustainable
   •  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 01:45:10 JST 

     in reply to

     • Angry Sun
     • eemmaa
     @eemmaa @sun Works as intended, yes.
     Screenshot_20240725_194427.png
   • eemmaa (eemmaa@soc0.outrnat.nl)'s status on Friday, 26-Jul-2024 01:45:11 JST eemmaa

     in reply to

     • Angry Sun

     @mint@ryona.agency @sun@shitposter.world here you go

   •  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 01:51:49 JST 

     in reply to
     This one went through as I was filtering for `_misskey_reaction` field, which is missing here together with `to`.
     Screenshot_20240725_194836.png
     Screenshot_20240725_195051.png
   •  (mint@ryona.agency)'s status on Friday, 26-Jul-2024 02:09:34 JST 

     in reply to
     Yeah, guess it's better to handle via MRF.
     https://gitgud.io/ryonagency/pleroma/-/commit/5eb3beb8b0e52b5371bb3a9c1c56f2bacb1aea13