14 - [-] Convert to Typed Racket
15 - [x] build executable (otherwise too-slow)
22 - see timeline ops above
27 - see timeline ops above
28 - see hashtag and channels above
31 - [ ] all - use all known peers
32 - [ ] fast - all except peers known to be slow or unavailable
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.
44 - [-] parse peer refs from peer timelines
45 - [x] mentions from timeline messages
46 - [x] @<source.nick source.url>
48 - [x] "following" from timeline comments: # following = <nick> <uri>
49 Rough sketch from late 2019:
53 let write file peers =
56 (* Fetch could mean either or both of:
57 * - fetch peer's we-are-twtxt.txt
58 * - fetch peer's twtxt.txt and extract mentioned peer URIs
63 let rec discover peers_old =
65 Set.fold peers_old ~init:peers_old ~f:(fun peers p ->
68 (* TODO: Should p be moved to down set here? *)
72 Set.union peers peers_fetched
75 if Set.empty (Set.diff peers_old peers_all) then
79 let rec loop interval peers_old =
80 let peers_all = discover peers_old in
81 let (peers_up, peers_down) = test peers_all in
82 write "peers-all.txt" peers_all;
83 write "peers-up.txt" peers_up;
84 write "peers-down.txt" peers_down;
86 loop interval peers_all
88 loop (Sys.argv.(1)) (read "peers-all.txt")
92 - [ ] nick tiebreaker(s)
93 - [ ] some sort of a hash of URI?
94 - [ ] angry-purple-tiger kind if thingie?
95 - [ ] P2P nick registration?
96 - [ ] Peers vote by claiming to have seen a nick->uri mapping?
97 The inherent race condition would be a feature, since all user name
98 registrations are races.
101 - [ ] download times per peer
102 - [ ] Support redirects
103 - should permanent redirects update the peer ref somehow?
104 - [ ] Support time ranges (i.e. reading the timeline between given time points)
105 - [ ] optional text wrap
107 - [ ] timeline limits
108 - [ ] peer refs set operations (perhaps better done externally?)
109 - [ ] timeline as a result of a query (peer ref set op + filter expressions)
111 - [ ] highlight mentions
112 - [ ] filter on mentions
113 - [ ] highlight hashtags
114 - [ ] filter on hashtags
115 - [ ] hashtags as channels? initial hashtag special?
117 - [ ] console logger colors by level ('error)
118 - [ ] file logger ('debug)
119 - [ ] Suport immutable timelines
120 - store individual messages
122 - something like DBM or SQLite - faster
123 - filesystem - transparent, easily published - probably best
124 - [ ] block(chain/tree) of twtxts
125 - distributed twtxt.db
126 - each twtxt.txt is a ledger
127 - peers can verify states of ledgers
128 - peers can publish known nick->url mappings
129 - peers can vote on nick->url mappings
130 - we could break time periods into blocks
131 - how to handle the facts that many(most?) twtxt are unseen by peers
136 - [x] caching (use cache by default, unless explicitly asked for update)
137 - [x] value --> cache
138 - [x] value <-- cache
140 - [x] Logger sync before exit.
141 - [x] Implement rfc3339->epoch
142 - [x] Remove dependency on rfc3339-old
143 - [x] remove dependency on http-client
144 - [x] Build executable
145 Implies fix of "collection not found" when executing the built executable
146 outside the source directory:
148 collection-path: collection not found
150 in collection directories:
152 /usr/share/racket/collects/racket/private/collect.rkt:11:53: fail
153 /usr/share/racket/collects/setup/getinfo.rkt:17:0: get-info
154 /usr/share/racket/collects/racket/contract/private/arrow-val-first.rkt:555:3
155 /usr/share/racket/collects/racket/cmdline.rkt:191:51
161 - [~] named timelines/peer-sets
162 REASON: That is basically files of peers, which we already support.