You don’t need a perfect global view to build smart feeds. Clients can query multiple relays, relays can share data, you can pay for indexing — there’s a whole design space there. Saying “NEVER” ignores all the creative stuff people could build.
It’s not about turning Nostr into something else — it’s about exploring what kinds of discovery work well within its structure. Open world, not closed door.
quotingI don't understand @fiatjaf's argument here, at least, I don't understand the *strength* of it ("NEVER") ? First, on "global feed", it's a bit like (a more extreme version of) "the mempool" - in a decentralized system there is no single synchronized global state, but .. there can be pockets of smaller synchronized state, at the relay level .. I guess even at the client level? If you have instant access to 10k or 100k messages your client can present them how it wants. I admit to not knowing much of anything about relays, so tell me if I'm wrong. If the answer involves "it's more expensive", remember it can be paid for; I already pay for relays, it's completely normal. Also, it has always been very obvious to me that the "social media" application of nostr would obviously benefit from algorithms for feeds. (though such a thing wouldn't magically make nostr suddenly popular).
nevent1q…gdff
nevent1q…m4lp