diff options
| author | Alex Auvolat <alex@adnab.me> | 2018-11-06 11:57:09 +0100 |
|---|---|---|
| committer | Alex Auvolat <alex@adnab.me> | 2018-11-06 11:57:09 +0100 |
| commit | c4f6cbab20b0b1d08755073d93365e5bd00dc755 (patch) | |
| tree | 384dd05c59a810d503790a2af1b5c49e1aed5ccf /TODO | |
| parent | 0e5b82f3348508eb7f4291a08722522a49edd752 (diff) | |
| download | shard-c4f6cbab20b0b1d08755073d93365e5bd00dc755.tar.gz shard-c4f6cbab20b0b1d08755073d93365e5bd00dc755.zip | |
Shard deletion ; update README and TODO
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 31 |
1 files changed, 17 insertions, 14 deletions
@@ -10,13 +10,16 @@ achieves our goals. TASK LIST ========= -- High priority: invite -- Medium priority: dht, dep +- High priority: invite, dht, groups +- Medium priority: net -Invitation system (invite, EASY) +Invitation system (invite, MED) -------------------------------- +Current issue: if a user PM's another user, that user does not know it! +He has to pull the PM shard voluntarily to get the messages. + A user may generate invitation tokens: an invite token is a signature of the invited user's pk by the inviter user's sk. The user that redeems the token writes some data that is saved temporarily in the user's identity shard, which @@ -39,7 +42,6 @@ Ex: keep 100 total open connections that are sampled by proximity on the set of plus 2 or 5 full random for all shards. - DHT to find peers for a given shard (dht, EASY) ----------------------------------- @@ -99,16 +101,6 @@ access control decisions (obviously these can only run when an identity with admin privilege is running). -Shard lifetime and dependency management (dep, MED) ----------------------------------------- - -Some Shards may pull other shards in, under certain conditions. For example -a stored folder shard will just be a list of other shards that we all pull in. - -We want a way to have toplevel shards, shards that are dependencies of -toplevel shards, and shards that we keep for a number of days as a cache but -will expire automatically. - COMPLETED TASKS =============== @@ -187,3 +179,14 @@ Best option: those that we are connected to + some random to reach a quota (for example 10 or so) Implementation: netgroups (lib/net/groups.ex) + + +Shard lifetime and dependency management (dep, MED) +---------------------------------------- + +Some Shards may pull other shards in, under certain conditions. For example +a stored folder shard will just be a list of other shards that we all pull in. + +We want a way to have toplevel shards, shards that are dependencies of +toplevel shards, and shards that we keep for a number of days as a cache but +will expire automatically. |