Skip to Content

Changes for page Definitions

Last modified by Zenna Elfen on 2026/02/16 14:43
From version 11.1
edited by Zenna Elfen
on 2026/02/16 14:43
Change comment: There is no comment for this version
To version 1.1
edited by Zenna Elfen
on 2025/11/23 23:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -P4P.WebHome
1 +P4P.Projects.WebHome
Content
... ... @@ -1,37 +1,21 @@
1 1  == Definitions for Authentication and Access ==
2 2  
3 -(% border="1" dir="ltr" id="auth_def" style="margin-right:auto" summary="Definitions for Authentication and Access" %)
3 +(% dir="ltr" id="auth_def" style="margin-right:auto" summary="Definitions for Authentication and Access" %)
4 4  |=Function|=What it means in P2P context
5 -|Permissions|//Define what actions a peer is allowed to perform (read, write, broadcast, modify state, etc.)//
6 -|Delegation|//Allow a peer to grant some portion of its authority to another peer (e.g., "you can write to this dataset for 1 day")//
7 -|Capabilities|//Tokens/objects that embody permissions and can be passed around securely//
8 -|Revocation|//Ability to withdraw access (essential yet tricky, since there's no central admin)//
9 -|(((
10 -Identity-agnostic control
11 -)))|//Often operations are authorized not by who you are but what capabilities you possess//
12 -|Custom Protocols |Internal term used by Iroh-crew to refer to protocols which are built by joining multiple different components together.
5 +|**Permissions**|Define what actions a peer is allowed to perform (read, write, broadcast, modify state, etc.)
6 +|**Delegation**|Allow a peer to grant some portion of its authority to another peer (e.g., "you can write to this dataset for 1 day")
7 +|**Capabilities**|Tokens/objects that //embody// permissions and can be passed around securely
8 +|**Revocation**|Ability to withdraw access (essential yet tricky, since there's no central admin)
9 +|**Identity-agnostic control**|Often operations are authorized not by //who// you are but //what capabilities you possess//
13 13  
14 -== ==
15 15  
16 -== Definitions for Architecture ==
17 17  
18 -
19 -|=Term|=Purpose|=Context
20 -|[[Grassroot System>>https://arxiv.org/abs/2301.04391v1]]|A grassroots system is a distributed system that can have multiple instances, independent of each other and of any global resources, that can interoperate once interconnected. Avoids "Singletons"|Examples are Activity Pub, Scuttlebutt
21 -|[[Singleton>>https://handbook.scuttlebutt.nz/stories/design-challenge-avoid-centralization-and-singletons]]|Singletons are networks which relies on being a whole "one" such as DHTs or global blockchains|Scuttlebutt, relates to Grassroot Systems
22 -
23 -== ==
24 -
25 -== ==
26 -
27 27  == Definitions for Security and Encryption ==
28 28  
29 -(% border="1" dir="ltr" id="sec_def" style="margin-right:auto" summary="Definitions for Security and Encryption" %)
15 +(% dir="ltr" id="sec_def" style="margin-right:auto" summary="Definitions for Security and Encryption" %)
30 30  |=Security Function|=Purpose|=Examples
31 31  |Transport Encryption|//P2P channel confidentiality//|//TLS, Noise//
32 -|[[Private Interest Overlap>>https://willowprotocol.org/specs/pio/index.html#private_interest_overlap]]|//allows peers to securely determine if they have capabilities in common without revealing what those capabilities are//|//Willow//
33 -|[[Prefix Pruning>>https://willowprotocol.org/specs/data-model/index.html#prefix_pruning]]|//Enables removal of data by replacing data with a new timestamped file that is empty, encouraging replication of the deletion.  "you have a path hierarchy which lets you prune off a whole bunch of leaves by cutting at the root. Like if you replaced your Documents directory with a text file of the same name."//|//Willow//
34 -|Message" Encryption|//End-to-end secrecy, async//|//MLS, Olm/Megolm, DR//
18 +|Message Encryption|//End-to-end secrecy, async//|//MLS, Olm/Megolm, DR//
35 35  |Identity & Trust|//Who’s who, key bootstrapping//|//DIDs, TOFU, Web-of-trust//
36 36  |Integrity|//Detect tampering//|//AEAD, Merkle DAGs//
37 37  |Key Lifecycle|//Rotation, revocation, recovery//|//X3DH, key transparency//