TODO

   1 # vim:sw=2:sts=2:
   2 TODO
   3 ====
   4
   5 Legend:
   6 - [ ] not started
   7 - [-] in-progress
   8 - [x] done
   9 - [~] cancelled
  10
  11 In-progress
  12 -----------
  13
  14 - [-] Convert to Typed Racket
  15   - [x] build executable (otherwise too-slow)
  16   - [-] add signatures
  17     - [x] top-level
  18     - [ ] inner
  19     - [ ] imports
  20 - [-] commands:
  21   - [x] r | read
  22     - see timeline ops above
  23   - [ ] w | write
  24     - arg or stdin
  25     - nick expand to URI
  26   - [ ] q | query
  27     - see timeline ops above
  28     - see hashtag and channels above
  29   - [x] d | download
  30     - [ ] options:
  31       - [ ] all - use all known peers
  32       - [ ] fast - all except peers known to be slow or unavailable
  33         REQUIRES: stats
  34   - [x] u | upload
  35     - calls user-configured command to upload user's own timeline file to their server
  36   Looks like a better CLI parser than "racket/cmdline": https://docs.racket-lang.org/natural-cli/
  37   But it is no longer necessary now that I've figured out how to chain (command-line ..) calls.
  38 - [-] Output formats:
  39   - [x] text long
  40   - [x] text short
  41   - [ ] HTML
  42   - [ ] JSON
  43 - [-] Peer discovery
  44   - [-] parse peer refs from peer timelines
  45     - [x] mentions from timeline messages
  46       - [x] @<source.nick source.url>
  47       - [x] @<source.url>
  48     - [x] "following" from timeline comments: # following = <nick> <uri>
  49   - [ ] Parse User-Agent web access logs.
  50   - [ ] Update peer ref file(s)
  51     Rough sketch from late 2019:
  52         let read file =
  53             ...
  54         let write file peers =
  55             ...
  56         let fetch peer =
  57             (* Fetch could mean either or both of:
  58              * - fetch peer's we-are-twtxt.txt
  59              * - fetch peer's twtxt.txt and extract mentioned peer URIs
  60              * *)
  61             ...
  62         let test peers =
  63             ...
  64         let rec discover peers_old =
  65             let peers_all =
  66                 Set.fold peers_old ~init:peers_old ~f:(fun peers p ->
  67                     match fetch p with
  68                     | Error _ ->
  69                         (* TODO: Should p be moved to down set here? *)
  70                         log_warning ...;
  71                         peers
  72                     | Ok peers_fetched ->
  73                         Set.union peers peers_fetched
  74                 )
  75             in
  76             if Set.empty (Set.diff peers_old peers_all) then
  77                 peers_all
  78             else
  79                 discover peers_all
  80         let rec loop interval peers_old =
  81             let peers_all = discover peers_old in
  82             let (peers_up, peers_down) = test peers_all in
  83             write "peers-all.txt"  peers_all;
  84             write "peers-up.txt"   peers_up;
  85             write "peers-down.txt" peers_down;
  86             sleep interval;
  87             loop interval peers_all
  88         let () =
  89             loop (Sys.argv.(1)) (read "peers-all.txt")
  90
  91 Backlog
  92 -------
  93 - [ ] Background polling and incremental timeline updates.
  94   We can mark which messages have already been printed and print new ones as
  95   they come in.
  96   REQUIRES: polling
  97 - [ ] Use ETag to prevent redundant downloads
  98 - [ ] Polling mode/command, where tt periodically polls peer timelines
  99 - [ ] nick tiebreaker(s)
 100   - [ ] some sort of a hash of URI?
 101   - [ ] angry-purple-tiger kind if thingie?
 102   - [ ] P2P nick registration?
 103     - [ ] Peers vote by claiming to have seen a nick->uri mapping?
 104           The inherent race condition would be a feature, since all user name
 105           registrations are races.
 106           REQUIRES: blockchain
 107 - [ ] stats
 108   - [ ] download times per peer
 109 - [ ] Support redirects
 110   - should permanent redirects update the peer ref somehow?
 111 - [ ] Support time ranges (i.e. reading the timeline between given time points)
 112 - [ ] optional text wrap
 113 - [ ] write
 114 - [ ] timeline limits
 115 - [ ] peer refs set operations (perhaps better done externally?)
 116 - [ ] timeline as a result of a query (peer ref set op + filter expressions)
 117 - [ ] config files
 118 - [ ] highlight mentions
 119 - [ ] filter on mentions
 120 - [ ] highlight hashtags
 121 - [ ] filter on hashtags
 122 - [ ] hashtags as channels? initial hashtag special?
 123 - [ ] query language
 124 - [ ] console logger colors by level ('error)
 125 - [ ] file logger ('debug)
 126 - [ ] Suport immutable timelines
 127   - store individual messages
 128     - where?
 129       - something like DBM or SQLite - faster
 130       - filesystem - transparent, easily published - probably best
 131   - [ ] block(chain/tree) of twtxts
 132     - distributed twtxt.db
 133     - each twtxt.txt is a ledger
 134     - peers can verify states of ledgers
 135     - peers can publish known nick->url mappings
 136     - peers can vote on nick->url mappings
 137     - we could break time periods into blocks
 138     - how to handle the facts that many(most?) twtxt are unseen by peers
 139     - longest X wins?
 140
 141 Done
 142 ----
 143 - [x] caching (use cache by default, unless explicitly asked for update)
 144   - [x] value --> cache
 145   - [x] value <-- cache
 146     REQUIRES: d command
 147 - [x] Logger sync before exit.
 148 - [x] Implement rfc3339->epoch
 149 - [x] Remove dependency on rfc3339-old
 150 - [x] remove dependency on http-client
 151 - [x] Build executable
 152   Implies fix of "collection not found" when executing the built executable
 153     outside the source directory:
 154
 155     collection-path: collection not found
 156       collection: "tt"
 157       in collection directories:
 158       context...:
 159        /usr/share/racket/collects/racket/private/collect.rkt:11:53: fail
 160        /usr/share/racket/collects/setup/getinfo.rkt:17:0: get-info
 161        /usr/share/racket/collects/racket/contract/private/arrow-val-first.rkt:555:3
 162        /usr/share/racket/collects/racket/cmdline.rkt:191:51
 163        '|#%mzc:p
 164
 165
 166 Cancelled
 167 ---------
 168 - [~] named timelines/peer-sets
 169   REASON: That is basically files of peers, which we already support.