Nah, that’s not quite right.
Tiny federates with huge - nothing happens, they just exchange metadata. Dancer@tiny subs to something on huge - now you have one community, with a lot of updates, coming at tiny. Maybe it drops some. Still not an issue
Hugo@huge subs to something on tiny - now something@tiny is cached on huge, still not a problem.
Now something@tiny is in the feed on huge. A million people comment. This is a problem… For huge mostly. Over at little, people are commenting on something@tiny. They might see doubled up comments or orphaned comments, but mostly they just don’t see most of the stuff from huge
So generally, it’s not an issue. In certain situations, there will be hiccups, but it will keep chugging along
It’s weird to think about, but data has a shelf life. Software needs to grow and be pruned regularly, or it dies.
Social media is both - the data dump is useless without an ecosystem of tools around it, and if the data itself stops interacting with the zeitgeist of the parent society, it basically becomes an old journal. It’s interesting to a very specific group of people, and literally no one else wants to see it (aside from a few gems picked out and cleaned up for public consumption)
At any point we could go back to Reddits explosion after the digg migration. We could pull up posts that mirror exactly what’s happening now. It’d be interesting for sure, and there’s days of then-now posts that people could be making…but instead we just have people telling us about their memories of that process.
Why? Because that data is old and stale. You’d have to hunt it down with tools not intended for it, filter out the best of it, fix broken links, and probably put it through a slur filter