06 June 2018 via IRC (#datprotocol)
- joehand
- pfrazee
- mafintosh
- bnewbold
- karissa
- bcomnes
- Review last meeting/action items
- AGENDA ITEM: Discuss updating dat-cli to use new DNS
- AGENDA ITEM: discuss Session Data Extension DEP dat-ecosystem-archive/DEPs#27
- AGENDA ITEM: Discuss Ephemeral Message Extension DEP
- (skipping DEPs/security updates)
- No update on heartbeat
- Dat DNS todos done
- hypercore data-structure identification headers
- Current approach is that all known data structures should follow the 1st message is a header message structure
- We need a DEP for that. It's pretty basic
- AGENDA ITEM: Discuss updating dat-cli to use new DNS
- implement https://github.com/datprotocol/dat-dns in dat CLI
- AGENDA ITEM: discuss Session Data Extension DEP dat-ecosystem-archive/DEPs#27
- lots of comments in gh
- mafintosh likes approach
- If this lands we should start having a list of official extensions btw
- If this lands we should start having a list of official extensions btw
- where list extensions?
- AGENDA ITEM: Discuss Ephemeral Message Extension DEP
- dat-ecosystem-archive/DEPs#28
- Mafinosh: idea here is good. But there are things I'd like to change
- Consider security
- And having a basic sequence number on them so they could be forwarded
- discuss more in GH PR
- Also you should consider having it be a protobuf, Easier to extend and not introduce a new encoding format
- Or making the header a varint for consistency
- List extensions somewhere on datprotocol.com (TBD)
- Hypercore data-structure headers
- DEP: all known data structures should follow the 1st message is a header message structure
- Message looks like this {protocol: stringName}
- @mafintosh
- Implement updated dat-dns in CLI (@joehand)
- merge draft of session data DEP (@pfrazee)
- Place to list extensions
- short proposal where to list (@pfrazee)
- discuss ephemeral msg extension in DEP PR (@mafintosh, @pfrazee)