aritter on Nostr: New milestone in rbr.bio development: threading in the feed view of a person mostly ...
New milestone in rbr.bio development: threading in the feed view of a person mostly works. Also view as is implemented for fun.
The goal of the feed view was to be a simple, self contained, but flexible implementation that is able to recursively load all parent events, merge threads, reorder threads (right now based on newest timestamp in the thread that is shown).
I'm planning to add minimal client features for playing with it better (like / reply / follow / login / maybe photos, make it super interactive, for example guarantee to show events from people that I replied to in a thread), but not planning to make it a client, as I'm more interested in creating a library for all clients that need feed support, which means that it has to be super flexible (showing comments, likes optional, recursive previous events optional, 100% customizable html / css).
One more thing that *has* to be flexible is ranking: first I'm planning to play with ranking myself, but make sure it's pluggable as well. With generic timeline the ranking function is easy-to compose (just take the minimum / maximum score of 2 threads when merging 2 threads into 1), but I'm not totally opposed to having much more complex ranking functions as well if they make sense and practical (that need all events in a thread and other metadata to compute a ranking function).
As I want to use Nostr as a Telegram / WhatsApp / HackerNews replacement for myself, my main ranking criteria will be the probablility that both I want to comment on a thread, and also I'm getting a comment reply. I know that many people care about likes / zaps, I care more about comments.
The goal of the feed view was to be a simple, self contained, but flexible implementation that is able to recursively load all parent events, merge threads, reorder threads (right now based on newest timestamp in the thread that is shown).
I'm planning to add minimal client features for playing with it better (like / reply / follow / login / maybe photos, make it super interactive, for example guarantee to show events from people that I replied to in a thread), but not planning to make it a client, as I'm more interested in creating a library for all clients that need feed support, which means that it has to be super flexible (showing comments, likes optional, recursive previous events optional, 100% customizable html / css).
One more thing that *has* to be flexible is ranking: first I'm planning to play with ranking myself, but make sure it's pluggable as well. With generic timeline the ranking function is easy-to compose (just take the minimum / maximum score of 2 threads when merging 2 threads into 1), but I'm not totally opposed to having much more complex ranking functions as well if they make sense and practical (that need all events in a thread and other metadata to compute a ranking function).
As I want to use Nostr as a Telegram / WhatsApp / HackerNews replacement for myself, my main ranking criteria will be the probablility that both I want to comment on a thread, and also I'm getting a comment reply. I know that many people care about likes / zaps, I care more about comments.