Thank you, this makes a lot of sense.
Although it's weird that some people want email to look more like DMs and you're making DMs look more like email.
Discussion
I think it was nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 who said once that people like email because it's stable and they know their messages are there waiting for them when they need them.
That's probably why email clients end up being the de facto RSS reader of many people with newsletter subscriptions, hence this idea for trying to get that to work in a Nostr context: nostr:nevent1qqsqqqx3n9ls2cu8qf5gxfhuzvt3kssv8v7etw20enna2t5yqkqj5xqppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qg3waehxw309ahx7um5wgh8w6twv5hschkr36
But now I'm thinking newsletters just fit the NIP-23 RSS style subscriptions better and mixing them up with email is a bad idea.
DMs are syncronous. Its like slack or chatrooms. a giant scrollback buffer with stuff that is easily missed, especially in groupchats. DMs are a denial of service attack when it comes to productivity.
Mails are focused, threaded topics that can be resolved in logical units. They are way more useful to me than DMs.
I get lots of messages on here with people having issues, if I could pin them in my inbox so that I can update that person over time as I fix issues, that would be ideal. I could tag a public nostr thread with a nostr-git-issue, and automatically update them when the issue closes.
Public threads are the closest thing to mail threads, it just needs a bit of design for managing them, like archiving when you're done with them.
The pinning stuff is very useful indeed. I hadn't thought about it until now but I wish I could pin some threads and answer them later, reference them later or update them later when some events happened. I don't know if an email inbox would be the best place for this though, maybe just a "notebook" indeed.