7 - [ ] Convert to Typed Racket
8 - requires: build executable (otherwise too slow)
10 Implies fix of "collection not found" when executing the built executable
11 outside the source directory:
13 collection-path: collection not found
15 in collection directories:
17 /usr/share/racket/collects/racket/private/collect.rkt:11:53: fail
18 /usr/share/racket/collects/setup/getinfo.rkt:17:0: get-info
19 /usr/share/racket/collects/racket/contract/private/arrow-val-first.rkt:555:3
20 /usr/share/racket/collects/racket/cmdline.rkt:191:51
23 - [ ] Support redirects
24 - should permanent redirects update the feed somehow?
25 - [ ] Support time ranges (i.e. reading the timeline between given time points)
26 - [x] Implement rfc3339->epoch
27 - [x] Remove dependency on rfc3339-old
28 - [x] remove dependency on http-client
29 - [ ] optional text wrap
31 - [x] caching (use cache by default, unless explicitly asked for update)
36 - [ ] feed set operations (perhaps better done externally?)
37 - [ ] timeline as a result of a query (feed set op + filter expressions)
40 - [ ] parse "following" from feed
41 - following = <nick> <uri>
43 - [x] @<source.nick source.url>
45 - [ ] highlight mentions
46 - [ ] filter on mentions
47 - [ ] highlight hashtags
48 - [ ] filter on hashtags
49 - [ ] hashtags as channels? initial hashtag special?
51 - [ ] console logger colors by level ('error)
52 - [ ] file logger ('debug)
55 - see timeline ops above
60 - see timeline ops above
61 - see hashtag and channels above
64 - calls user-configured command to upload user's own feed file to their server
65 Looks like a better CLI parser than "racket/cmdline": https://docs.racket-lang.org/natural-cli/
66 But it is no longer necessary now that I've figured out how to chain (command-line ..) calls.
67 - [ ] Suport immutable timelines
68 - store individual messages
70 - something like DBM or SQLite - faster
71 - filesystem - transparent, easily published - probably best
72 - [ ] block(chain/tree) of twtxts
73 - distributed twtxt.db
74 - each twtxt.txt is a ledger
75 - peers can verify states of ledgers
76 - peers can publish known nick->url mappings
77 - peers can vote on nick->url mappings
78 - we could break time periods into blocks
79 - how to handle the facts that many(most?) twtxt are unseen by peers
85 rough sketch from late 2019:
89 let write file peers =
92 (* Fetch could mean either or both of:
93 * - fetch peer's we-are-twtxt.txt
94 * - fetch peer's twtxt.txt and extract mentioned peer URIs
99 let rec discover peers_old =
101 Set.fold peers_old ~init:peers_old ~f:(fun peers p ->
104 (* TODO: Should p be moved to down set here? *)
107 | Ok peers_fetched ->
108 Set.union peers peers_fetched
111 if Set.empty (Set.diff peers_old peers_all) then
115 let rec loop interval peers_old =
116 let peers_all = discover peers_old in
117 let (peers_up, peers_down) = test peers_all in
118 write "peers-all.txt" peers_all;
119 write "peers-up.txt" peers_up;
120 write "peers-down.txt" peers_down;
122 loop interval peers_all
124 loop (Sys.argv.(1)) (read "peers-all.txt")