wooo, this is great @andrestaltz!

agree this breaks some assumptions in the current replication implementation, but i think it's a good step in the right direction and we should improve our replication systems to be more flexible in regards to network / social graphs.

it would still make sense to change the gossip scheduler so that it disconnects as soon as (plus a few seconds) its done downloading the recent updates from a pub, and then go on to visit the next pub, and keep rotating.

but then we'd miss the benefits of long-term connections, low-latency live updates and less connection handshakes.

How hard would it be to change this to replicate a specific id + the people followed by that id?

i like this idea, which i'd describe as config.hops = 1 not 2.