Updated TODO.

TODO.md

@@ -2,7 +2,7 @@
 
 ## Open
 
-Implement bulleted lists.
+Implement bulleted lists. Mastodon is crap and won't show them, but other instances (Friendica, Pleroma) will do.
 
 Add a purge timeout also for the local timeline.
 
@@ -12,13 +12,11 @@ Implement HTTP caches (If-None-Match / ETag).
 
 The 'history' pages are now just monthly snapshots of the local timeline. This is ok and cheap and easy, but is problematic if you e.g. delete a post because it will be there in the history forever.
 
-Create the `mastodon2snac` helper program (reading directly from the boxes, not using any exported data).
-
 Add an RSS to the local timeline.
 
-Implement hashtags.
+Implement hashtags. They are not very useful, as they can only be implemented as instance-only (not propagated), but it may help classifiying your own posts.
 
-Idea for a new disk layout: timelines stored like in git (2 character directories and then the md5.json inside); one append-only index with entry ids, read backwards (easy because md5 binary ids measure the same); children lists as append-only files stored inside the timeline directories with almost the same names as the parent entry; liked-by and announced-by lists as append-only files of actor ids. No _snac metadata inside the message. (But, what about the referrer? With this layout, do I need it?).
+Idea for a new disk layout: timelines stored like in git (2 character directories and then the md5.json inside); one append-only index with entry ids, read backwards (easy because md5 binary ids measure the same); children lists as append-only files stored inside the timeline directories with almost the same names as the parent entry; liked-by and announced-by lists as append-only files of actor ids. No _snac metadata inside the message (But, what about the referrer? With this layout, do I need it?). The instance storage may even be global, not per user; this could help in very bing instances (but will this be a use-case for snac? not probably).
 
 ## Closed