3 ms·
Look at how much chaos came from just adding a few million people in a month. I don't see a way that goes better adding tens of millions in the same or shorter
by Kye 4y ago
Look at how much chaos came from just adding a few million people in a month. I don't see a way that goes better adding tens of millions in the same or shorter period. The best way for Tumblr to do it would be to:
1: Open source it
2: Make it federated with other Tumblrs. Probably using whatever BlueSky cooks up, or some similar effort focused on big platforms.
3: Offer a managed version the same way they do with WordPress for the majority of people who don't want to run their own
4: Provide an optional ActivityPub extension
5: Telegraph that federation is coming for the still probably too big main instance(s) to give administrators time to decide how they'll handle it: mute, block, allow, etc. This gives people who eventually migrate off in 6/7 a clear view of how instances plan to handle it.
6: Add ActivityPub support to the main instance(s). Make it opt-in.
7: Wait to see how it shakes out as people migrate to non-Tumblr instances. By now, probably 2-3 years in, there will be enough diversity in platforms and hosting options that most people will have some place to go that's appealing. We already see minimal AP instance software popping up that focuses on providing people with a Linktree/Caard-like experience where it's only a profile that's exposed to AP instances. Maybe even sites like that will add AP support! Posts from these could replace newsletters. (I know, a common claim for as long as newsletters have existed)
- sylvietg 4y agoTumblr already effectively federates inside its own network. Instead of accessing <blog>.tumblr.com, log in at tumblr.com and then visit tumblr.com/<blog>. Each user must have one blog. A user can create more blogs and a blog may have more than one contributor. Only primary blogs can comment, like, etc. What I would personally do is copy Mastodon's approach. This is super easy and pain free and doesn't require messing with Hellsite's architecture and potentially ticking off thousands of users while simultaneously playing better with Mastodon, specifically. How do I accomplish this? By creating a proxy for each Federated entity the first time it is needed. Tumblr's local API continues to just operate against local entities, tagging the proxy when needed. A separate process batches outbound notifications, grouping by target server. Inbound, I just locate or create the proxy for the given federated entity - then use the existing deliver infrastructure to deliver the notification. This also gives me a good way to cache content - and allows local trust and safety to do their thing if they need to. It limits all code changes related to this to the edge of my network, limiting the risk.