dirkmc

@satazor I like this idea 👍 I think it would be good to also refactor the persistence service into a separate repo

Considerations for a leadership election protocol: - We already have - a mechanism for gossiping membership changes to all peers in the collaboration - a [membership summary hash](https://github.com/ipfs-shipyard/peer-star-app/blob/master/src/collaboration/membership.js#L156): a hash...

@pgte when Alice finds that Bob is unreachable, Alice will evict Bob from her membership list and gossip that out to other peers in urgent mode, right? I was imagining...

As @pgte pointed out, when there is a collaboration partition but not an IPNS partition, one leader will be elected on each side of the partition and they will overwrite...

That makes sense. Hopefully it should be rare that there is a network partition that splits the collaboration but does not split IPNS. In an ad-hoc network the non-interactive election...

I wanted to think through how a Raft style leader election would work concomitantly with peer-star membership gossip in a few different scenarios. The first four scenarios are similar to...

I've created a separate WIP PR against this branch with an implementation of leadership, so that this PR doesn't get too big: https://github.com/dirkmc/peer-star-app/pull/1

@pgte are you asking about creating a feat/persister branch on peer-star-app and merging dirkmc:peer-star-app/feat/persister into it? I'm not sure I see the advantage?

FYI I have written an [implementation of leadership](https://github.com/dirkmc/peer-star-app/pull/1). Today I wrote [several test scenarios](https://github.com/dirkmc/peer-star-app/pull/1/files#diff-6f7624f614823f5281d736d44156118f) for leadership. Next I need to - [x] write a few more test scenarios for leadership...

I have completed the tests for leadership and have been testing out leadership persistence with a real-world example app. Some issues I've come across: - It takes several seconds to...