4 ms·

> That person then boosts a post from another server and they have effectively DDOSed that server. All the other nodes will start querying that server about tha

> That person then boosts a post from another server and they have effectively DDOSed that server. All the other nodes will start querying that server about that post or image. But that's fixable in several ways - local media cache for an instance, the boost including the preview rather than each client fetching it for themselves, etc. The problem* with ActivityPub is that it's been designed and developed in a bit of user vacuum and it definitely has issues but they can all be worked on. Much like Twitter going from Rails to Scala, etc., to fix their issues.

georgyo 4y ago
There is already a local media cache. My comment doesn't suggest that each follower requests stuff from the home server, but each instance. The instances cache pretty aggressively, but you still have a thundering herd when a popular person boosts a message.
- zimpenfish 4y ago
  > There is already a local media cache. I suppose I should have been clearer - apologies. I was talking about a cache for previews (which would presumably be folded into the local media cache since it's already there.) > you still have a thundering herd when a popular person boosts a message Not if the boost includes the preview - that -should- cut it down significantly (and indeed it has been proposed but is still being bikeshedded by the Mastodon devs because "what if someone sends a fake preview?!?!?!?!")