Conversation

Notices

1. Embed this notice
   boyter (boyter@honk.boyter.org)'s status on Wednesday, 11-Jan-2023 03:40:34 JST boyter

   in reply to

   • marius
   @mariusor Except that creating a valid activitypub actor is trivial as I was able to do with mastinator. In effect trillions on trillions of valid actors.

   If you really want to not distribute your posts, don't post them on a federated system.

   One option I am playing around with is using hashcash as a way to slow it down. Forcing people to pay a cpu cost to get the content would allow legitimate actors to get it, and in theory slow down bad actors.

   • Embed this notice
     marius (mariusor@metalhead.club)'s status on Wednesday, 11-Jan-2023 03:40:35 JST marius

     @boyter the answer to this is so simple. Interacting with any end-point needs to have an HTTP Signature corresponding to a valid ActivityPub actor. This actor should be a Service for instances of fediverse servers, an Application for non client applications, a Person for client applications like Toot! or Tusky.

     This way there's a simple indicator where the requests originated and what/who needs to be blocked if the traffic is un-wanted.