do nip17 clients handle threaded replies?
Discussion
i would hate to have my inbox in my DMs, i feel like having them separate would be a good thing
Mine ignore the subject tag and reply hierarchies, but there's no reason you couldn't add them
having them interoperable might be interesting for sure, i just don't want to spam DM clients with broken stuff
I don't think ot would be too broken to naively merge threads. Maybe a little confusing, but it would nudge implementations to support the full spec
thoughts nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ?
i also think the UX is a bit different. DMs are built around long term conversations between individuals.
inboxes are short term conversations around topics.
I personally think it's better if we migrate NIP-17 to be for mail like stuff. Day to day DMs are better suited for Marmot (NIP-EE)
Someone had already created a prototype or design for it. He was working on a nostr client of his own or just designing it not sure. Don't remember his name and can't find him in my follows now either
now that I have the high performance giftwrap hammer I want to start using it for everything. marmot is a lot more complex in comparison
Found it, it was nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q , now need to find his post
This is the post, I am not sure if Niel thought about making it interoperable with existing DMs but I liked the design and it was in my mind since then to make an email like interface for NIP-17 DMs
nostr:nevent1qqs0le2nayu8gnetmn0nng356wt7ctaa0wpk9ly7dxesxsqcn4kp33g40e3qm
We show the parent reply inside the chat buble itself. Subject renames the group chat to whatever people want.
If you want to group by subject (like email), you might need a new kind. Kind 14 requires grouping by the people in the group, like discord/slack does.
I don't know if I like threading to do email-like things, created at order is so good.
yeah i'm definitely leaning toward a new kind nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck