PigeonProtocolConsortium/Protocol-Spec
PigeonProtocolConsortium
/
Protocol-Spec
5
4
Fork 1
Code Issues Pull Requests Releases Wiki Activity

Fix typo, add mailing list.

This commit is contained in:
Netscape Navigator 2020-06-29 08:47:21 -05:00
parent 606eedf8af
commit 989809bfe9
3 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -350,6 +350,8 @@ to allow for partial verification of message feeds.
# Getting involved with the Pigeon protocol development
**PIGEON PROTOCOL DEVELOPERS MAILING LIST:** Send an email with "subscribe" in the subject line to `pigeon_developers@vaporsoft.xyz`.
If you want to be involved with the Pigeon protocol development, there
are areas we need help in currently:

5
bundles.md
View File

@ -1,5 +0,0 @@
# Bundle File Specification (WIP)
We will draft this specification after the first client is finished- we've found that too many things have changed since the start of the project.
Please see this [Lexer](https://tildegit.org/PigeonProtocolConsortium/pigeon_ruby/src/branch/master/dist/pigeon/lexer.rb), written in Ruby, that can help you build your own bundle-consuming code:

2
message_format.md
View File

@ -66,7 +66,7 @@ Every Pigeon database has an "identity". An identity is an ED25519 key pair that
The steps to generate a valid identity are:
1. Perform [Crockford Base32 encoding](https://www.crockford.com/base32.html) on an ED25519 public key.
2. Concatenate the characters `FEED.` to the beginning of the string from step 1.
2. Concatenate the characters `USER.` to the beginning of the string from step 1.
### Line 2: `Kind`