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]

Reply to this note

Please Login to reply.

Discussion

Doesnt "relays" solve is problem.. o had thos problem yesterday and i cleaned my feed by messing with the relays.. its not Twitterwe dont need an algorithm.. lol mess with the relays lol

How?

You see those green Icons the little world. The group of people you can turn those on and shut those off and it'll mess with your feet. You? Clean up your feet a little bit.

That doesn't solve the UX problem I just described.

1. When you view 80% of new content on your feed, you have to rescroll through that same 80% before getting to the last, unread 20% of content.

2. When a popular noot gets boost flooded, it can dominate your feed until the boosting ceases.

Relays don't fix this, AFAICT bud.

Well jack flood my feed yesterday and i cleaned it up messing with relays.. lmao again its not Twitter we need to get Twitter featurs out of our head this is #nostr learn the relays i fixed .y feed yesterday

Welcome tobthe world of relays lmao much love πŸ§‘πŸ’œπŸ§‘πŸ’œπŸ§‘πŸ’œπŸ§‘πŸ€™πŸΎπŸ€™πŸΎπŸ€™πŸΎ

It could happen with any note from any user. Idy we move towards a proper feature that balances out the UX.

Notice in this picture I shut off the noster wine relay