Add docs about storage backend

[friendica.git] / spec / zot-2012.txt

diff --git a/spec/zot-2012.txt b/spec/zot-2012.txt
index b223a27eaf7102332716dd8f7780015378dd3b66..3d939bab73653c7b95d13a82d84885a2c95ecde2 100644 (file)
--- a/spec/zot-2012.txt
+++ b/spec/zot-2012.txt
@@ -11,12 +11,12 @@ First create a global unique userid
 Site userid:
 https://macgirvin.com/1
 
-$guuid = base64url_encode(hash('whirlpool','https://macgirvin.com/1.' . mt_rand(1000000,9999999),1);
+$guuid = Strings::base64UrlEncode(hash('whirlpool','https://macgirvin.com/1.' . mt_rand(1000000,9999999),1);
 
 
 Then create a hashed site destination.
 
-$gduid = base64url_encode(hash('whirlpool', $guuid . 'https://macgirvin.com',1);
+$gduid = Strings::base64UrlEncode(hash('whirlpool', $guuid . 'https://macgirvin.com',1);
 
 These two keys will identify you as a person+site pair in the future.
 You will also obtain a password upon introducing yourself to a site.
@@ -66,7 +66,7 @@ POST https://example.com/post
 'person' => $guuid
 'address' => $new_gduid
 'site' => 'https://newsite.com'
-'info' => 'mike@macgirvin.com'
+'info' => 'mike@newsite.com'
 'pass' => me_encrypt($gduid . '.' . $pass)
 }
 
@@ -135,6 +135,12 @@ Returns:
 Message
 -------
 
+Passing messages is done asynchronously. This may (potentially) relieve a lot of the burden of distribution from the posting site. If you're on site 'A' and make a post, site 'A' just contacts any downstream sites and informs them that there is new content (via a $post_id). The downstream site initiates the actual data transfer. 
+
+
+
+
+
 POST https://example.com/post
 
 {
@@ -155,9 +161,10 @@ Returns:
 Callback
 --------
 
-POST https://macgirvin.com
+POST https://macgirvin.com/post
 
 {
+'type' => 'retrieve'
 'retrieve' => $post_id
 'challenge' => you_encrypt('abc123')
 'verify' => me_encrypt('xyz456' . '.' . $gduid)