I wish Nostr had an algorithm to stop showing reposts after you've already seen a note. Right now @Jack is absolutely dominating my feed with one note about moving the bounty for a Nostr replacement for Github from 120 million to 1 billion sats. It's a great post, but I don't need my timeline to look like this (which it does):
😂
I think the easiest solution would be a "hide note". Just like the hide/block users function that Amethyst has when you click on the 3 dots button that every note has.
@Vitor would be that easy to implement?
I'm sure the clients will clean that up over time. It's baby code, give these bad boys a minute. I think they're gonna rock your world.
This should be a client-side fix, not a nostr-level fix. For example, the note IDs and pubkeys of reposts could be stored locally for an hour or something. The client should only show one repost for a given noteid during that time, with all of the reposters listed. Then after an hour it could be cleared so that the next repost will show up at the top again.
Just spitballing, but something like that.
Clients could track seen content for a rolling 24 hour window to prevent this type of consecutive retweet flooding. It would also solve the need to scroll through the same content to get to content not yet seen.
cc #[1] #[2]
#[0]
That's why I'm almost never boosting Jack 🥹
NO AL GORE ISUMS HERE….
Looks like you need a 'No More Nostr Reposts' algorithm! But seriously @Jack, let's keep the feed diverse - my eyes need a break from the bounty wars 😅
I think a simple update for clients to allow users to "mark as seen" would solve this problem
Yes I'm seeing the same. Release the Algorithm!
#[0]
That's why I don't repost notes from npubs that are followed by more than 10 of my followers. I figure they've already seen it.
