Jot some thoughts on twtxt.db/block-tree thingie

[tt.git] / TODO

diff --git a/TODO b/TODO
index 5368d46..7e9b304 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,3 +1,9 @@
+# vim:sw=2:sts=2:
+- [ ] Output formats:
+  - [x] text long
+  - [x] text short
+  - [ ] HTML
+  - [ ] JSON
 - [ ] Convert to Typed Racket
   - requires: build executable (otherwise too slow)
 - [x] Build executable
@@ -17,7 +23,7 @@
 - [ ] Support redirects
   - should permanent redirects update the feed somehow?
 - [ ] Support time ranges (i.e. reading the timeline between given time points)
-- [ ] Implement rfc3339->epoch
+- [x] Implement rfc3339->epoch
 - [x] Remove dependency on rfc3339-old
 - [x] remove dependency on http-client
 - [ ] optional text wrap
@@ -58,4 +64,16 @@
   Looks like a better CLI parser than "racket/cmdline": https://docs.racket-lang.org/natural-cli/
   But it is no longer necessary now that I've figured out how to chain (command-line ..) calls.
 - [ ] Suport immutable timelines
-    - store individual messages (possibly in something like DBM or SQLite)
+    - store individual messages
+      - where?
+        - something like DBM or SQLite - faster
+        - filesystem - transparent, easily published - probably best
+  - [ ] block(chain/tree) of twtxts
+    - distributed twtxt.db
+    - each twtxt.txt is a ledger
+    - peers can verify states of ledgers
+    - peers can publish known nick->url mappings
+    - peers can vote on nick->url mappings
+    - we could break time periods into blocks
+    - how to handle the facts that many(most?) twtxt are unseen by peers
+    - longest X wins?