diff --git a/TODO.md b/TODO.md index 6436986..1277674 100644 --- a/TODO.md +++ b/TODO.md @@ -2,9 +2,7 @@ ## Open -Add a user-settable `local_purge_days`. - -There are some hosts that keep returning 400 Bad Request to snac posts (e.g. hachyderm.io). I've investigated but still don't know where's the problem. +There are some hosts that keep returning 400 Bad Request to snac posts (e.g. hachyderm.io). I've investigated but still don't know where the problem is. Add a list of hashtags to drop. @@ -20,7 +18,9 @@ With this new disk layout, hidden posts (and their children) can be directly ski ## Wishlist -Refactor the queue to be global, not per user. +Move the output messages to the global queue. + +Refactor the global queue to use a pool of threads. Implement the ActivityPub C2S (Client to Server) API: (https://www.w3.org/TR/activitypub/#client-to-server-interactions). The client at http://andstatus.org/ implements it. @@ -30,6 +30,8 @@ The 'history' pages are just monthly HTML snapshots of the local timeline. This Implement bulleted lists. Mastodon is crap and won't show them, but other implementations (Friendica, Pleroma) will do. +Add a user-settable `purge_days`. This is not at first very hard to do, but purging posts from a user cache directory does not also delete them from the global object database and they will be kept in the indexes (unless they are also deleted from the indexes, which is a too expensive operation); this way, if another user in the same instance follows you, your posts will not disappear as you desire and that may be confusing and annoying. A different way to implement this: configure a maximum number of entries to keep and truncate the indexes in the purge. But this does not clear the disk usage, which is why I want to implement this (to implement bots that generate posts periodically and avoid the disks exploding). + ## Closed Start a TODO file (2022-08-25T10:07:44+0200). @@ -209,3 +211,5 @@ Integrate https://codeberg.org/alderwick/snac2/commit/a33686992747f6cbd35420d23f Add support for editing our own messages (2023-01-25T18:36:16+0100). 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 (2023-01-26T14:39:51+0100). + +Refactor the queue to be global, not per user (2023-02-03T20:49:31+0100).