Sonya Mann
Sonya Mann ✅Per @kodo's discussion with Gargron, a person's posts only make it to the federated timeline if someone on your instance is following that person. IMO this is a design flaw — it encourages centralization on one big instance (so that you can see entire conversations and find new people easily) even more than it encourages cross-instance links.
For me this is even more of a value-killer than not being able to bring your followers with you from instance to instance (and ironically if the latter were possible it would help with the former).
🏴☠️🏴☠️KODO🏴☠️🏴☠️@sonya Bringing your followers with you would be a huge undertaking https://xkcd.com/1425/
Andrea@sonya not doing that would be a quadratic scaling disaster, with every post having to be broadcast to every instance in the limit
@puellavulnerata what are you talking about, tradeoffs are a myth!
🔜@@puellavulnerata @sonya gossip protocols, tho
@puellavulnerata @sonya they way I've seen stuff like that get implemented (for between nodes in a datacenter) is you basically have three protocols: a point-to-point one for unpopular content, a fanout spanning tree for medium popular, and a gossip protocol for the most popular content
@parataxis @sonya doesn't help; N nodes r rate of message production per node, each node needs bandwidth N r, total N^2 r
@puellavulnerata @sonya you don't gossip everything, just the content that passes some popularity threshold
Rysiekúr (old account)@sonya it would, yes - but I guess "small steps". ;)
@sonya Although he did say that it does a recursive follow for threads, so that is a bonus. He says that's more than what gnu social does so I'll call it a win.
@sonya @kodo there's no easy fix for that - traffic grows exponentially with number of users and instances, if all federated with all by default, it would be unmanageable. That's where p2p networks are better - but also so much harder to do (look at #Twister ) #KeepCalmAndFederate
@rysiek I do like your hashtag a lot