Yup 🎯
Apps reading from a set of relays defined by the Communities (or the App's goal).
Solves the global state problem too, at the local community level.
I like this.
I think Damus also displays the zaps like that, right nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszythwden5te0dehhxarj9ekxzmny9uqzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9ffz2xl?
But does your client make it so people only read replies from that specific relay? Because I think that's a step in the path to solving spam.
Discussion
Yeah, I've never gotten the concept of using relays full of people I don't like.
We are allow-oriented.
* Everyone on the community relays is allowed.
* People on your lists, or events from query results, are also allowed. (We pull those from "fallback" relays.)
* Events from your local relays are also allowed.
Yup.
It's the UX around all of this "allowing" that I'm still working out rn.