@ev The latest batch of ferment leakage is my fault. I noticed some ferment posts in my patchwork data feed that weren't showing up (someone must have been using another pub with ferment) and I wanted to see if they'd get sucked across if I paired my two ssb directories on my computer. It worked perfectly. Only ferment feeds were replicated into my ferement instance and those missing posts showed up.

But the side effect was of course that my patchwork now has my ferment account as a friend, so it went ahead and 3-hop replicated me and everyone else on ferment. This is great for ferment because it means people can now use other pubs (not just my one).

I think the network is working as intended. We just need a better way of handling these duplicate identities. This is already a problem (lost keys, multiple devices). Me and @mikey had a good discussion about this last night.

@Dominic I have a short term proposal for handling at least the naming conflicts. Ferment could use a namespaced field for its name field. When someone changed their name on ferment, we'd generate this message { type: 'about', name: 'ferment_matt', scoped_name: 'matt' } ... or { type: 'about', scope: 'ferment' } (second option would require co-operation with other clients)