is it ok if we start to see a trend of clients building timelines/feeds from their own databases?
say i want to build a timeline of top/trending posts from a relay or under a topic- it is probably better if a client scraps tons of data from a relay into a db, sorts events in the db to create this timeline and serves it to the user from the db instead of the relay.
this is a direction i see- thoughts #[0]? this would be pretty harmful for relay diversity tho
you would post to relays as normal, or find replies/links directly from relays. it’s just for building the timeline view
These would not be strict clients according to the spec, so it's probably an anti-pattern and potentially a centralization vector, but it's happening and we can't prevent it. I think it will probably be ok as long as there is client diversity and people get used to moving between clients.
How about a separate relay that shows the most popular posts from last 24h or something? Is that preferred? I think we could make that.
Yes, that would be great. I do want to see an app that allows one to browse relay global feeds kind like they were websites. https://github.com/alemmens/nuestr is going that way, but slowly.
I still think https://github.com/nostr-protocol/nips/pull/259 could help provide this additional second-layer functionality in a less-than-centralized way, without putting the burden of switching on end users.
I'm guilty of this, but I just want my pow list to be like a little taste of pow (until at least one client has sort by pow).
I would work on a client, but I don't think anyone would use the kind of client I'd want. So https://powrelay.xyz/explore is just there to nudge the people that make user-friendly clients.
