The repository provides some controls for outbound connections (deliveries), but does nothing to throttle inbound requests. As mentioned, this is usually a configuration of your webserver or middleware (PHP-FPM) and to me it seems silly to replicate what they're doing at another layer in the stack. ActivityPub is a really chatty protocol and very little concern has been given to letting people know when the actor record needs to be updated, so as you add connections and make public posts, you're going to be hit with inbound requests for your actor record and profile photo by a significant percentage of them in a very short period of time - every time you post. And we would attach the actor record to the post and save a round trip, but most fediverse software would crash because they aren't expecting a complete record - only a URL. This is just an example but that's what we're up against.
That's the situation, and I'm not claiming it's ideal. I welcome any efforts to improve how we handle this - but at the moment PHP-FPM configs are the best option available.
Hexit
IRC Chat
Tic-Tac
