From 758639f48f5aad73ebe03b8cd598915b51a1fb53 Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sun, 21 Aug 2022 18:00:48 +0200
Subject: [PATCH] autopushed

---
 agora pkg chapter.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/agora pkg chapter.md b/agora pkg chapter.md
index 17bc7cbea..64340cdb1 100644
--- a/agora pkg chapter.md	
+++ b/agora pkg chapter.md	
@@ -202,6 +202,14 @@ Go links provide an interest base case to study in the field of provisioning and
 
 The primary utility, though, is high. In a [[go links]] rich environment, users can depend on other users to have defined [[canonical links]] for named [[entities]]; that is, collections of specially relevant resources to the terms at hand, as shared in a [[commons]]. 
 
+Put simply, [[go links]] are named bookmarks -- strings of text (usually slugged, but not necessarily) associated with URLs by users in a community. 
+
+- Go links provide an [[individual]] function: they allow the user to associate a (usually short) string with a resource of interest, and then recall it from any computing with network access with a short deterministic flow.
+  - Sharing documents becomes simpler by definition in a community of practice that is go links aware. Instead of locating a resource and invoking a sharing flow to share, users are able to say to each other 'go thisdoc' (meaning either go/thisdoc or go/this-doc by convention), effectively transferring a URL in spoken word very efficiently, depending only on a previously understood mechanism to resolve such links (at a well known point, ideally a [[schelling point]]). 
+  - The trivial extension case for them is social bookmarking.
+
+An example would suffice. You could reme
+
 ## Pull
 
 ## Push