mafintosh / mafintosh/hyperlog
describe replication protocol?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 469
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to understand how your replication protocol works. I looked at the code but there is quite a bit going on. this comment gives me the impression that [hyperlog is a scuttlebutt?](https://github.com/mafintosh/hyperlog/issues/11#issuecomment-154855251) but other things have given me the impression that hyperlog can fork? is it just forks in a different sense? I also remember you where working on a thing that traces the graph out.
how does it handle different replication cases? how does it behave if an update was concurrent or not?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the replication protocol in the code and reviewing the linked discussion about whether Hyperlog is a scuttlebutt log or can fork. Document how replication handles forks, graph tracing, and concurrent versus non-concurrent updates; the issue is done when these cases are explained clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100