checkpointing

src/comparison/activitypub.md

@@ -0,0 +1 @@
+# ActivityPub

src/comparison/at_protocol.md

@@ -0,0 +1,16 @@
+# AT Protocol/Bluesky
+
+```{index} Identity
+```
+```{index} Bluesky
+```
+```{index} Identity; DID
+```
+
+We aren't too concerned with billionaires cosplaying as altruists and the technologies they produce, but the AT Protocol has a few ideas, particularly related to [identity](https://atproto.com/guides/identity), that are interesting.
+
+Specifically, AT protocol differentiates between *handles* and *identities*, where DNS entries are used as short handles that resolve to a [DID](https://www.w3.org/TR/did-core/).
+
+That's about it, the rest of the handling of DID's is extremely centralized (see [did:plc](https://atproto.com/specs/did-plc) which requires resolution against a single domain), and the requirement of all posts to be funneled through [Big Graph Services](https://blueskyweb.xyz/blog/5-5-2023-federation-architecture) rather than directly peer to peer is transparently designed to ensure a marketing and advertising layer in between actors in the network.
+
+

src/comparison/bittorrent.md

@@ -0,0 +1 @@
+# BitTorrent

src/comparison/hypercore.md

@@ -0,0 +1 @@
+# Dat/Hypercore

src/comparison/index.md

@@ -2,26 +2,30 @@
 
 All of this is TODO. Comparison to existing protocols and projects (just to situate in context, not talk shit obvs)
 
-## "The big ones"
+```{toctree}
+:caption: P2P
 
-- BitTorrent
+bittorrent
-- IPFS
+ipfs
+hypercore
+```
 
-## "The research ones"
+```{toctree}
+:caption: Social
 
-- Dat
+activitypub
-- Hypercore
+ssb
+matrix
+at_protocol
+```
 
-## Social
+```{toctree}
+:caption: Linked Data
 
-- ActivityPub/Fediverse
+solid
-- Secure Scuttlebutt
+ld_fragments
-- Matrix
+nanopubs
-
+```
-## Semweb/LD
-
-- SOLID
-- Nanopubs
 
 ## To be categorized
 

src/comparison/ipfs.md

@@ -0,0 +1 @@
+# IPFS

src/comparison/ld_fragments.md

@@ -0,0 +1 @@
+# Linked Data Fragments

src/comparison/matrix.md

@@ -0,0 +1 @@
+# Matrix

src/comparison/nanopubs.md

@@ -0,0 +1 @@
+# NanoPubs

src/comparison/solid.md

@@ -0,0 +1 @@
+# SOLID

src/comparison/ssb.md

@@ -0,0 +1 @@
+# Secure Scuttlebutt

src/conf.py

@@ -37,6 +37,12 @@ html_baseurl = '/docs/'
 # -----------
 # Extension config
 
+# myst
+myst_heading_anchors = 3
+myst_enable_extensions = [
+    'tasklist'
+]
+
 # Napoleon settings
 napoleon_google_docstring = True
 napoleon_numpy_docstring = True

src/data_structures.md

@@ -29,6 +29,7 @@ Triplet graphs similar to linked data fragments with envelopes. decoupling conte
 - Format: A container can specify one or several ways it can be displayed 
 - Capabilities: A container can specify different capabilities that another account can take (eg. "Like", "Upvote", "Reply")
 	- Capabilities should also contain a permissions scope, if none is present, the global scope is assumed.
+	- Since Identities are just a special form of container, they too can advertise different actions that they support with capabilities.
 
 
 

src/definitions.md

@@ -1 +1,15 @@
 # Definitions
+
+Putting there here to remind me to use the glossary directive... (these are not real definitions yet, just placeholders)
+
+```{glossary}
+
+Identity
+    A unique cryptographic identity. One person may have multiple identities. One identity may have one or several {term}`Petname`s and {term}`Beacon`s
+
+Petname
+    A short name used to refer to a {term}`Identity`. Petnames are always contextual: `@Alice` referring to `@Bob` has the status of "The person that @Alice knows as @Bob." A petname can be declared by the identity being referred to as a "canonical" petname, but since they are potentially nonunique they should always be dereferenced against the Identity making the reference.
+
+
+
+```

src/identity.md

@@ -22,7 +22,7 @@ A given identity can have 0 or many bidirectional links indicating that the iden
 - Subscribers to a given identity MUST store and represent the known aliases and treat them as equivalent
 - Other accounts can give an alias to an identity that MAY be accepted (by issuing a backlink) or denied (by ignoring it).
 
-### Succession
+### Rotation
 
 An identity has a specific field indicating whether it is "active" or "retired," and can issue a special top-level link with given permission scope indicating the identity that succeeds it.
 	- eg in the case of harrassment, one can hop identities and only tell close friends.

src/index.md

@@ -8,13 +8,14 @@ This site describes the implementation of the p2p linked data protocol in {cite}
 :caption: Introduction
 
 overview
-comparison
+comparison/index
 p2p_concepts
 out_of_scope
-```
+```  
 
 ```{toctree}
 :caption: Protocol
+:numbered:
 
 definitions
 protocol