Conversation

Notices

1. Embed this notice
    (mint@ryona.agency)'s status on Friday, 16-Feb-2024 20:36:34 JST 
   Some porn bots are spamming retweets despite no one on my server following them.
   Screenshot_20240216_143457.png
   Screenshot_20240216_143514.png
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 20:39:46 JST FrailLeaf

     in reply to
     @mint the porn committee decided that it'll be that way
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 20:40:34 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf It might be spamming inboxes of its whole peerlist. So far seems like there's only one other person that took notice of that.
     https://github.com/michaelcpuckett/ap-groups/issues/44
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 20:42:50 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf "turned off" my ass.
     https://github.com/michaelcpuckett/activity-kit/issues/11
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 20:43:19 JST FrailLeaf

     in reply to
     @mint lol spam protocol at it again
      likes this.
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 20:49:48 JST FrailLeaf

     in reply to
     @mint
     > Activities addressed to this special URI shall be accessible to all users, without authentication.
     
     :heyface:
      likes this.
   • Embed this notice
     Ethical Pedophile (blinkrape@posting.lolicon.rocks)'s status on Friday, 16-Feb-2024 20:50:14 JST Ethical Pedophile

     in reply to
     @mint working as intended
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 20:50:53 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf That's the essence of public scope, yes. No matter how many fetches have to be signed.
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 20:58:32 JST FrailLeaf

     in reply to
     @mint UGH I am retarded. The spec suggests to use sharedInbox to not overwhelm the network and he QUOTES it but still says "lole nmp". Where is he actually delivering to lol
     image.png
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 20:59:58 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf He does deliver to shared inbox, yes. Still, majority of current server implementations only send out activities if there's at least one subscribed actor to deliver them to, be it an actual user or a relay.
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 21:19:17 JST FrailLeaf

     in reply to
     @mint so
     >the remote/receiving server participates in determining targeting and performing delivery to specific inboxes.
     >Origin servers sending publicly addressed activities to sharedInbox endpoints MUST still deliver to actors and collections otherwise addressed (through to, bto, cc, bcc, and audience) which do not have a sharedInbox and would not otherwise receive the activity through the sharedInbox mechanism.
     
     is pleroma not implementing any of these checks and just gobbling up stuff
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 21:20:19 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf I think that's intended behavior, at least if Announce activity has the public constant in to/cc.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 16-Feb-2024 21:21:29 JST 

     in reply to

     • FrailLeaf
     @FrailLeaf And yeah, it does.
     Screenshot_20240216_152101.png
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Friday, 16-Feb-2024 21:44:28 JST FrailLeaf

     in reply to
     @mint literally spam protocol :spinsanity:
      likes this.