More comments from the outline

README.org

@@ -7,8 +7,33 @@
 
 ** ActivityPub
 
+# - ActivityPub is an actor model protocol.
+# - The general design can be understood from the overview section of the spec
+
+# - In general, most of the design of ActivityPub is fairly clean, with
+#   a few exceptions
+
+#   - sharedInbox is a break from the actor model protocol and was a late
+#     addition
+#   - authentication is not specified
+#   - authorization is not specified
+#   - (json-ld conversations outside of the scope of this particular post)
+
+# - What to do about the holes in the spec?  Many community members have
+#   asked that we codify current behavior.  However, as this document lays
+#   out, some of the ways those holes were filled may be causing problems
+#   and we may want to consider how to best redirect them without throwing
+#   out the network as it has been deployed.
+
+# - Nonetheless, ActivityPub has achieved major adoption.  ActivityPub
+#   has the good fortune that its earliest adopters were frequently
+#   people who are actively concerned with human rights and the
+#   well-being of marginalized groups.
+
 ** The mess we're in
 
+
+
 ** Don't pretend we can prevent what we can't
 
 ** Freedom of speech also means freedom to filter
@@ -36,14 +61,19 @@ problems if they're the foundation".)
 * Key concepts
 ** Object capabilities (ocaps)
 
+# - 
+
 *** Ocaps meet ActivityPub objects/actors
 
+
 ** True names, public profiles, private profiles
 
 ** Accountability and revocation in an ocap system
 
 ** Rights amplification and group-style permissions
 
+** multiBox vs sharedInbox
+
 * Limitations
 
 * Future work