sounds like it would use a LOT of events.. but you could have relays that specifically are for impressions if you really wanted this. anything's possible 💫
Wait this sounds dope
nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgwwaehxw309ahx7uewd3hkctc58hv2s what u think about impressionable nips?
Discussion
my event store already has an index that maintains a last accessed time... it would be simple enough to add a counter field to that record but i'm not sure how you'd structure a query to learn it, that would be a whole addition to the protocol
i made that record type to implement a garbage collector, as part of a second level store... that reminds me i need to re-add the GC to the relay
Each user could have 1 event for the last 1000 notes (by event is) they've viewed or an event for every note they've ever viewed. Then clients can req for that event and populate views similar to how they populate follows.