@Russell
Nostr enjoyer
Relays (4)
- wss://nostr-01.yakihonne.com – read & write
- wss://relay.damus.io – read & write
- wss://relay.primal.net – read & write
- wss://relay.nmail.li – read & write
Recent Notes
Hey we're not using a custom protocol, We are using WKD, which protonmail also uses, so it's interoperable
Of course, WKD is the protocol to use for this.
I was talking about creating the WKD entry and others things like folders, labels, signatures...
Are you writing specifications so people can easily understand your protocol without doing some kind of reverse engineering?
I was talking about creating the WKD entry and others things like folders, labels, signatures...
Are you writing specifications so people can easily understand your protocol without doing some kind of reverse engineering?
2
Having said that we do have a lot of features on top that are extra like WKD PGP encryption implemented on top of nip-44, and domain routable mails ofcourse. I'm not sure if NMail has it, but it'd be...
Hello, I would like to implement PGP in Nmail. Are you publishing your protocol specification somewhere ? It would be useful so we can discuss about it and converge. You can use Openspecsif you want 😉
https://openspecs.uid.ovh/
https://openspecs.uid.ovh/
1🤙1
If you ask for my email, you also get my npub
"@Russell@uid.ovh "
"@Russell@uid.ovh "
> my bridge was refusing the email because the from address was too long
Wow, that must be an important fix then; I see the emails from GH now, thanks!
Another thing I noticed is that alias probably...
Private aliases were never migrated to the new bridge architecture. Thank you for this precious information, it's now resolved.
💜1
Some mails never reach the inbox; I wasn't able to receive GitHub verification emails in particular. I'm curious, does GitHub connect to the bridge in practice, or it doesn't show any sign of attempti...
I enabled DNSec for both domains. About the emails that were never reaching the inbox, I fixed it today.
Github was connecting to the bridge but my bridge was refusing the email because the from address was too long (above 64 characters before the "@"). Typically, the issue occurred when using the base36 hex or npub format as your address.
Github was connecting to the bridge but my bridge was refusing the email because the from address was too long (above 64 characters before the "@"). Typically, the issue occurred when using the base36 hex or npub format as your address.
1
Looks like `app.nostrmail.org` is currently down.
Does the server responded or it is an empty screen ?
1
Know of https://github.com/nogringo/nostr-relay
Specifically built by nostr:nprofile1qqsty2cxkpgl653jje4fx39xxnv4ds7uxwnltmxu4k0dz8wugys20uspr4mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mf0qy2hwumn8g...
I created it because no others relays care about DM privacy. I updated NIP 59 yesterday to fix a privacy issue. And implemented the updated spec today inside the relay.
https://openspecs.uid.ovh/spec/npub1kg4sdvz3l4fr99n2jdz2vdxe2mpacva87hkdetv76ywacsfq5leqquw5te/nip-59
https://openspecs.uid.ovh/spec/npub1kg4sdvz3l4fr99n2jdz2vdxe2mpacva87hkdetv76ywacsfq5leqquw5te/nip-59
☕1
nostr:nprofile1qqsty2cxkpgl653jje4fx39xxnv4ds7uxwnltmxu4k0dz8wugys20uspr4mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7w60x...
Not at the protocol level. I see 2 solutions:
Remote signer, run a bunker on your key and give the other npub a connection scoped to nip44_decrypt only. They read your mail, they never hold your nsec, and you can revoke the connection any time. Closest thing to real read delegation today.
Auto-forward. Your client or a script decrypts and re-wraps incoming mail to their npub. Works with any client on their side, but the copy is signed by you, so the original sender proof is lost.
Remote signer, run a bunker on your key and give the other npub a connection scoped to nip44_decrypt only. They read your mail, they never hold your nsec, and you can revoke the connection any time. Closest thing to real read delegation today.
Auto-forward. Your client or a script decrypts and re-wraps incoming mail to their npub. Works with any client on their side, but the copy is signed by you, so the original sender proof is lost.
1
