As a closing point, I can see a point where the protocol evolves to seamlessly include #UX wise #SingleTenant instances without bringing all the server-centric baggage, thus promoting an inclusive leveled playing field for all sorts of federation scaling strategies: #VerticalFederation, #HorizontalFederation and #FlatFederation. (And as a plus, improve #mastodon #onboarding #friction issue too.)

As for I, intend to engage in that discussion and contribute to this extraordinary #foss project.

But, if I may add a few lines on #FlatFederation, I also feel that sometimes Mastodon might be (still) too server-centric at times.

Sometimes it almost feel we've embraced #federation but not fully (perhaps because we've been living in a server-client world for too long and only now trends like Web3, whatever that means, are becoming more mainstream/common).

To tackle this I see three generic scaling strategies emerging from the discussion:

#VerticalFederation akin to @Gargron/mastodon.social, scaling 'up' the most popular servers to keep up with demand.

#HorizontalFederation advocating a more fragmented/decentralized ecosystem with servers breaking up into smaller instances, and solutions like account count limits.

#FlatFederation advocating mostly for a greater #SingleTenant approach, where everyone should set up their own mastodon server.