Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Thursday, 09-Mar-2023 12:54:40 JST Alex Gleason

   • ToxicPositivity

   I have a plan for dealing with this. Hope they don’t eat my disk space before I get to it.
   
   RT: https://mostr.pub/objects/801b37fe5656848534a96599201729fe923651c5815d7bb219991db685b62a9c

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Thursday, 09-Mar-2023 13:00:06 JST Alex Gleason

     in reply to

     • ToxicPositivity
     • pwm

     @3baabe4d008648b5438bfe3180e3d443cbc36478fbabb65007099a96a1c56922 @0a970d6ce29aabbdfda6aec40e53ea034324caf7d5775f7dc1b9983fc4ec5b1b Basically I already filter out Nostr events by a certain criteria before I even let them hit the pipeline in the bridge: https://gitlab.com/soapbox-pub/mostr/-/blob/develop/src/nostr/handler.ts#L111-119

     I just need to lift this logic out into a strfry policy. It means the mostr relay will be essentially read-only until you get a fedi follower, but for federation we read data from a pool anyway.

   • Embed this notice
     pwm (3baabe4d008648b5438bfe3180e3d443cbc36478fbabb65007099a96a1c56922@mostr.pub)'s status on Thursday, 09-Mar-2023 13:00:07 JST pwm

     in reply to

     • ToxicPositivity
     Planning to do verified via nip-05 only? I saw some discussion of that as a spam deterrence measure yesterday.