pzp
/
pzp-wiki
mirror of https://codeberg.org/pzp/pzp-wiki.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

List a few more differences

This commit is contained in:
Jacob Karlsson 2024-05-23 17:24:20 +02:00
parent 33b4e46f36
commit 5814d903a5
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
guide/intro.md
View File

@ -25,11 +25,14 @@ What it doesn't specify:
- Multi device/app support from the start. Every device/app has its own keypair. They're connected together into one identity using an Account tangle. The Account tangle's root message ID is the account's identifier. - Multi device/app support from the start. Every device/app has its own keypair. They're connected together into one identity using an Account tangle. The Account tangle's root message ID is the account's identifier.
- One account or even keypair can post messages concurrently (forking) without problem. Because there aren't linear feeds, everything is in tangles. - One account or even keypair can post messages concurrently (forking) without problem. Because there aren't linear feeds, everything is in tangles.
- Deletion is possible. The data contents of a message is separate from the message metadata, and only the metadata + hash of the data is signed. - Deletion is possible. The data contents of a message is separate from the message metadata, and only the metadata + hash of the data is signed.
- When messages are getting signed they get serialized according to [RFC 8785](https://tools.ietf.org/html/rfc8785).
- Easy to use invites
### How PZP is different from Nostr ### How PZP is different from Nostr
- keys are not shared across devices - keys are not shared across devices
- sig-chains - you know if you're missing content in PZP - sig-chains - you know if you're missing content in PZP
- trust based - invite only
## Tangles ## Tangles