update TODO

1 files changed, 22 insertions, 9 deletions

diff --git a/TODO b/TODO
index 690ce62..177f292 100644
--- a/TODO
+++ b/TODO
@@ -10,7 +10,7 @@ achieves our goals.
 TASK LIST
 =========
 
-- Highest priority: comm, sign, ep
+- Highest priority: comm, privchat, ep
 - Medium priority: dht, dep
 
 
@@ -78,17 +78,20 @@ infrequently used pages, for examples those of old data that is only
 kept for archival purpose.
 
 
-Signed stuff, identity management (sign, MED)
----------------------------------
+Private chat (privchat, MED)
+------------
 
-We want all messages that are stored in our data structures to have
-a correct signature from a certain identity.
+Proof-of-concept for private things: shard for private chat between two people.
 
-We can have a special "identity" shard type that enables storing
-profile information such as nickname or other information that we
-might want to make public.
 
-Proof-of-concept: shard for private chat between two people.
+Invitation system (invite, EASY)
+--------------------------------
+
+A user may generate invitation tokens: an invite token is a (sk, pk) plus a
+signature of pk by the user's sk.  The user that redeems the token writes some
+data signed by sk that is saved temporarily in the user's identity shard, which
+might be stored by a 3rd party node for instance if we are on mobile devices
+that cannot connect directly.
 
 
 User groups and access control (groups, req: sign, HARD)
@@ -168,3 +171,13 @@ we are sure serialization is unique and hash is the same everywhere.
 
 Terminology: stop using the word "block", use "page" everywhere.
 
+
+Signed stuff, identity management (sign, MED)
+---------------------------------
+
+We want all messages that are stored in our data structures to have
+a correct signature from a certain identity.
+
+We can have a special "identity" shard type that enables storing
+profile information such as nickname or other information that we
+might want to make public.