I think we're gonna see a divide between apps "built on nostr" vs "interacting with nostr".
I may be retarded but it seems like there's potential for abuse or carelessness that could strain relays if they're treated like free distributed databases for app infrastructure. If I'm a relay operator, I might not want a nostr-based exchange's orderbook data hogging resources.
What's the solution?
I'm not even sure if the distinction here is a legit one. I haven't thought it through enough.
🤔
My first guess is that relays will start filtering events based on the kind tag (in fact that functionality already exists for some relays for kind 1984).
I figured aggressive filtering would be necessary but how that gets balanced with potential censorship concerns is what I'm trying to think through
yeah think you’re right, but built on and interacting with are both fine. but, if i was building an app i’d consider it essential to be community minded - build out good relays to take the weight of my app, but also serve the community in return for the community of relays providing some redundancy for me. also, some sats mechanism per event relayed would incentivise operators.
True tho you can't rely on the goodness of man at scale, unfortunately. The free rider issue will become apparent without costs attached. Paid interactions will solve for a lot of that but that also presents some issues as well in terms of whether people want to bear that cost (not financially, but psychologically)
