pull down to refresh
131 sats \ 3 replies \ @k00b 7 Oct 2023 \ parent \ on: Lyn Alden book club part I bitcoin
That's helpful. It sounds like you might want an aggregate of what you've missed rather than a stream of everything that's happened.
I think this would be useful in all our conversation notifications - not just subscriptions. I'll think on it more.
A trivial way that might help a bit is the notification provides some relevant sub-tree to contextualize the thing. At a minimum this could be the parent, but perhaps there could be more interesting ways to do it.
Notifications could also "roll up" the changed state (complete w/ relevant context) since you last saw it. Or maybe that's what you mean? That's probably what you mean.
I can imagine that re-loading a page (e.g,. this one) could have everything that was here last time I loaded the page be dimmed; everything new to me appears in its current illumination; and everything that would be an update (e.g., my own posts that have been zapped, replies to things I've said) would be highlighted or something. So the change set is easy to spot, and the relevant-to-me changeset is even easier?
reply
That's probably what you mean.
Yep!
I can imagine that re-loading a page (e.g,. this one) could have everything that was here last time I loaded the page be dimmed; everything new to me appears in its current illumination; and everything that would be an update (e.g., my own posts that have been zapped, replies to things I've said) would be highlighted or something. So the change set is easy to spot, and the relevant-to-me changeset is even easier?
Yep that's what I'm thinking to address the problem that this solution implies: Feature request: option to archive seen posts
Feature requests are often the wrong solution to the right problem ... is what I like to say.
reply
Sounds great, thanks!
reply