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

FAQ cleanup

This commit is contained in:
Netscape Navigator 2020-04-28 07:31:22 -05:00
parent f82eb0a115
commit 1ea9b53186
2 changed files with 3 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
FAQ.md
View File

@ -24,14 +24,7 @@
# Is This a Blockchain?
It's different than a block chain despite some similarity
Pigeon has no singletons. Each participant maintains their own chain.
There is no global blockchain (or any global anything really)
If you trust someone, you agree to replicate their chain (called a "feed")
you also replicate the feed of their peers creating the concept of "listening distance"
This is how Secure Scuttlebutt is achitected, so I can't take any credit for that idea.
The messages can also contain blobs and references to other feeds (like links)
So if I'm friends with you, and you're friends with Tunas, I can browse Tunas' blobs and text entries
It's different than a block chain despite some similarity. A global blockchain is a singleton, and Pigeon has no singletons. Each Pigeon node maintains their own feed of messages rather than sharing a global feed. When you trust a peer, you agree to replicate their feed. You also replicate the feed of their peers. Unlike a blockchain, there are many feeds (rather than one) and they do not require consensus to coexist. Additionally, forking of feeds is not supported by Pigeon.
# Up Next

6
README.md
View File

@ -135,11 +135,9 @@ The [first working implementation of a Pigeon protocol client](https://tildegit.
* Configuration is always a design comprise. We will allow a limit of 10 configuration options for all eternity. These are simple key/value pairs. No nesting, no namespacing, no dots, no dashes, no nested config names, no arrays, none of that crap. Seriously, I'm watching you.
* Assume CPU and RAM are not plentiful.
* Assume platform has no networking support. No servers. No hooks for startups, shutdowns, or reboots.
* Assume CPU resources and memory are limited.
* Assume block storage is plentiful when making resource allocation tradeoffs.
* Files are better than sessions.
* ...but be filesystem agnostic. Persistence mechanisms are implementation-specific.
* Provide tamper resistance. Privacy features will be added in v2.
* Files are better than sessions, but be filesystem agnostic. Persistence mechanisms are implementation-specific.
* Provide tamper resistance. Privacy features will be added later.
* Enable "Free listening"
* Have a formal specification (reference implementations are not OK).
* Minimize conceptual overhead (If it's not needed at least 80% of the time, don't add it).