now, I'm still trying to work out some user-friendly way to optionally offer some form of "stable" timelines in #snac, namely, if I reload a timeline page (say after a browser restart, reboot, accidental reload, whatever) I get back to the same spot I was, or if I advance to the next page in that timeline whether after minutes or days, I get predictable and repeatable results, rather than something that moves every time it's reloaded

currently, I'm creating dated marker posts only visible to myself, and creating lists of posts by selecting a range of lines from private.idx into say list/20250201.idx, while creating list/20250201.id with "2025-02-01". then I can navigate that list, and keep it for as long as I wish. but that's not very user-friendly. I suppose I could create some interface to create (and delete) such lists over the web.

before finding out about lists, my plan was to enable the use of &latest= (whether md5 or local post's timestamp id), so that I could then start navigating a timeline with a fixed starting (or rather ending) point. it would then start counting skip at that post, rather than at the very latest post in the private timeline.

this could be made more user friendly by enabling the use of one's own posts as reference points for timeline browsing (which would add that post's id as &latest= in a link off of that post), or by offering an alternate current timeline link that created the marker post and used its id as &latest=. these artificial marker posts could be recognized and omitted from the timeline, if that seems desirable.

WDYT?

CC: @grunfink@comam.es