@dansup I'm not sure what's to be done to solve the media storage problem... imagining that the fedi continues to grow at any pace, won't this become an unavoidable roadblock at some point?

@dansup Not really. Yes there will be more choices of people to follow. More medias. More interactions. More servers charges. But it’s always proportional to the initial size of our instance.

Fortunately, each server does not federate all Fediverse actors.

@dansup But why would that happen? The size of an instance doesn't affect the load they put on other servers, the number of interactions does. Mastodon.social (>200k) puts no more load on my server than Mastodon.art (<10k), for example. Tumblr would be no different in that regard, surely?

Maybe I'm missing something?

@dansup i think tumblr should lean harder into indieweb stuff than into activitypub tbh -- i feel like using activitypub for microblogging is not exactly ideal. i look at things such as "rss to activitypub" bots as kind of misguided because you should just be able to follow the rss feed. activitypub should be about delivering notifications and user activity. consider how Announce works, and then think about how it doesn't map onto tumblr, but microformats u-repost-of works fine up the chain...

@dansup frankly, someone like tumblt joining is a real test for the viability of the federation model. Mastodon.social should be further fragmented. It's a landing space before people find an instance that works for them.

@dansup Tumblr is actually in the position to "present" as a collection of separate instances (one per blog), which would significantly reduce many of the practical issues that would be associated with them joining as a single instance. Whether they'll do this, though, is a different matter.