250bpm

If all nodes on a bus are homogeneous, who binds the socket?

User does. He decides which nodes are bound, which connect or which do both. However, after the topology is set up all the nodes act in the exactly same way.

I think the need for a forwarding raw bus connecting each totally connected sub-bus makes this no use for a friend to friend topology (sparsely connected peers, no hub), and that's a pity.

What I wonder is, could this be extended to the more general case of a sparsely connected group, so every member still receives every message it didn't send, only once? Perhaps, each broadcast contains the ID of the sender, but also the IDs of the receivers, and a message UUID, so each recipient can forward it to its connections that aren't named (adding them to the list), and discard messages whose UUID it has seen (they looped around).