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