nielliesmons on Nostr: Any current Nip-17 DM is already defined and acts more like a mail (size don't ...
Any current Nip-17 DM is already defined and acts more like a mail (size don't matter).
It's a private text event, sent to a specific set of profiles, that has a subject and can reference previous events.
It just misses some crucial features:
- (optional) deeper thread history
- (optional) signing of the main event ā Anything serious needs this (marketplaces f.e.) for dispute resolution.
- mailbox relays that give upfront info about the conditions for publishing in someone's inbox
We have other Nips for truly private rooms, Nip-17 is not that use-case. It can be very awesome for professional mailing, one-of communication, ... anything/anyone that you don't want to set up an actual chat room for.
š Where I'm already building in the Mail UX:
- Satshoot: jobs and services, marketplace comms
- Zapcloud: mails for warnings when you run out of budget etc...
- Communikeys: a one-to-one Mail tab that can
exist next to the Community chat with zero confusion, etc...
- Actual email: maps very well on the sort of messages people would like to get forwarded to their legacy inbox
I'm not the guy to spec this out (but I will if no one else does).
I'm the guy that sees the obvious UX/UI error apps currently make with Nip-17.
Published at
2025-06-06 07:37:30Event JSON
{
"id": "3aa7e024bdba564a88e602b2883f553e3804c946cdf3189ffb4f49839299324a",
"pubkey": "a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"created_at": 1749195450,
"kind": 1,
"tags": [
[
"e",
"0843ce1c58584fc1429b6c15696ad9db42f0361f1f664728a7475400ff038a40",
"wss://nos.lol/",
"root",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"e",
"0843ce1c58584fc1429b6c15696ad9db42f0361f1f664728a7475400ff038a40",
"wss://nos.lol/",
"reply",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"emoji",
"110percent",
"https://cdn.satellite.earth/60a5e73bfa6dfd35bd0b144f38f6ed2aaab0606b2bd68b623f419ae0709fa10a.png"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "Any current Nip-17 DM is already defined and acts more like a mail (size don't matter).\n\nIt's a private text event, sent to a specific set of profiles, that has a subject and can reference previous events.\n\nIt just misses some crucial features: \n- (optional) deeper thread history\n- (optional) signing of the main event ā Anything serious needs this (marketplaces f.e.) for dispute resolution.\n- mailbox relays that give upfront info about the conditions for publishing in someone's inbox\n\nWe have other Nips for truly private rooms, Nip-17 is not that use-case. It can be very awesome for professional mailing, one-of communication, ... anything/anyone that you don't want to set up an actual chat room for. \n\nš Where I'm already building in the Mail UX: \n- Satshoot: jobs and services, marketplace comms\n- Zapcloud: mails for warnings when you run out of budget etc...\n- Communikeys: a one-to-one Mail tab that can :110percent: exist next to the Community chat with zero confusion, etc...\n- Actual email: maps very well on the sort of messages people would like to get forwarded to their legacy inbox\n\nI'm not the guy to spec this out (but I will if no one else does).\nI'm the guy that sees the obvious UX/UI error apps currently make with Nip-17. ",
"sig": "c329dfe331280512c1ff7026c3c7b4fdd8cc5e9349e4b71cc8fd3ed4c0b63427a99e98d9b75672d37283da06d8aa8a2912c6078e6dd9a1552e4e2282683bbd37"
}
