Paul Frazee

WIP: Peer Discovery DEP

1

This one is almost ready to go. Needs review and a few TODO items which should be easy to resolve. TODOs - [ ] add a section about hole punching...

Proposal & Discussion: Hypercore "major version" pointer

3

One of the current issues with Hypercore is that a fork in the history is a fatal corruption of the data. This means that peoples' datasets can be destroyed by...

Remove hyperdrive-specific material from the hypercore spec

1

I noticed that we have a hyperdrive-specific description of using a `metadata` and `content` feed in the intro of this spec. I think that's somewhat misleading (especially because it characterizes...

Include heartbeat rate in the hypercore-protocol handshake

3

It turns out that peers need to agree on the heartbeat rate, otherwise they'll incorrectly detect a dead connection. For instance, if peer A expects a rate of 1 every...

Change "title" to "name"

6

I think it might be good idea for Beaker to change from "title" to "name", because that's what the Web manifest.json and the WebExtensions manifest.json specs use, and we want...

Git repo URL

1

We've been thinking about getting better git integration into beaker's workflows, and to do that we'd want to add a repository link to the dat.json. How would folks feel about...

version

2

Another attribute I'd like to propose: `version`. It would be an optional string. Does not have to be a semver. It reflects the most recent checkpoint.

Argument for using public key for the path, instead of discovery key

1

The argument for using discovery keys for the folder paths is to make it so you can't enumerate a user's dats with an `ls`. Counter arguments: 1. I actually want...

We should create a new spec doc for the `dat://` URL

https://github.com/datprotocol/web-specs/blob/master/dat-protocol.md is currently empty. We need to describe its behaviors.