Skip to content

Add NIP-M4: Email#2391

Open
nogringo wants to merge 1 commit into
nostr-protocol:masterfrom
nogringo:nip-m4-email
Open

Add NIP-M4: Email#2391
nogringo wants to merge 1 commit into
nostr-protocol:masterfrom
nogringo:nip-m4-email

Conversation

@nogringo

Copy link
Copy Markdown

No description provided.

@fiatjaf

fiatjaf commented Jul 2, 2026

Copy link
Copy Markdown
Member

Given the number of people who have expressed liking the idea of "email on Nostr" in the past I expected this to have more feedback.

Since no one has come I'd leave mine: I think this makes no sense. There is nothing good about the email format, and this wouldn't be email. We need one good Nostr-native messaging protocol, not another standard for messaging, but this time all encoded in weird plaintext and then it isn't compatible with normal email anyway, of course.

If the idea is making bridges to normal email, why not make the bridge to NIP-17?

@nogringo

nogringo commented Jul 2, 2026

Copy link
Copy Markdown
Author

Bridge to nip17 was my first idea but the nip17 client UI are not suited for emails. It work well to receive magic link / otp but when you want to reply, things get complicated.

There are also some feature that need a dedicated protocol:

  • public emails
  • large emails (more than 64 KB)
  • sorting / labeling

@fiatjaf

fiatjaf commented Jul 2, 2026

Copy link
Copy Markdown
Member

I'm beginning to see your point.

But why is it a problem to reply from NIP-17?
Why can't you sort/label NIP-17 messages?

@vitorpamplona

Copy link
Copy Markdown
Collaborator

I think a newl kind with its own formatting rules and rendering needs is needed.. reusing nip 17 will just overload the chat kinds with stuff they don't want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants