Re: "Evolving ActivityPub to reduce infrastructure costs"

you can get a lot of the way there with HTTP/2 and persistent connections,
which reduced mastodon fanout costs significantly when we implemented it.
HTTP/3 might be even better with its reduced head-of-line blocking

On Wed, Mar 15, 2023 at 10:10 PM Evan Prodromou <evan@prodromou.name> wrote:

> So, I will say that I have heard this, too, but more about the cost of
> fanout than the cost of each delivery.
>
> It's a hard problem.
>
> I think it might be possible to reduce fanout costs somewhat by keeping
> frequently-used server to server connections open and making deliveries
> using, for example, WebSockets.
>
> But that would require a change in the server protocol.
>
> It would be cool to experiment with, though.
>
> On Mar 15, 2023 22:13, Benjamin Goering <ben@bengo.co> wrote:
>
> > I just think that if there is an impression “out there” by some people
> that ActivityPub needs to be evolved "to reduce infrastructure costs” then
> this group here should be aware of that.
>
> It’s hard to tell for sure whether there is an impression out there like
> this from this thread because the only evidence you presented was that you
> heard someone say it.
> It would indeed be helpful if you invite your acquaintance to share some
> first-hand report to the list.
>
> > On Mar 15, 2023, at 15:55, Johannes Ernst <johannes.ernst@gmail.com>
> wrote:
> >
> > I just think that if there is an impression “out there” by some people
> that ActivityPub needs to be evolved "to reduce infrastructure costs” then
> this group here should be aware of that.
>
>
>