jb55 on Nostr: I was thinking about this the other day when trying to design email on nostr. I was ...
I was thinking about this the other day when trying to design email on nostr. I was trying to model a relay as a mailing list, then you would need some syntax for ccing your message to a specific relay.
We have nprofile or nip05+relays for @ing a specific person and their origin relays, but not if I want to cc a message to a relay which may hold one or more mailing lists 🤔
This would start moving us to a much more decentralized model, at least in the email case, but now I'm thinking how these ideas work in the social case
We have nprofile or nip05+relays for @ing a specific person and their origin relays, but not if I want to cc a message to a relay which may hold one or more mailing lists 🤔
This would start moving us to a much more decentralized model, at least in the email case, but now I'm thinking how these ideas work in the social case
quoting note1w07…c53vSometimes when I’m in the thick of building things I forget the grander implications of the tools I’m putting out there. Thank you Max DeMarco (npub1lel…kvyz) for reminding me of that. I need to make damus more decentralized and make it better at communicating with different relays.
A good mental model for this is that right now damus CCs every relay you’re connected to. Once its easier to CC specific relays then lots of new use cases pop up.
Maybe this should be more apparent in the UI, and less mass-CCing everything.
This is in the same territory as the gossip model, but the UX story is still evading me.