Last Notes
I'm not blaming them. They tried and lost. Then we lost too. Now we are the last generation that isn't all fake and gay
I'm saying the entire country has been gay for 3 generations, that is why they aren't reproducing and why they are opening their borders. AfD is the reform they need, but the likelihood it's real is near zero. To claim the Russian datacenters contain bots that are run by Russians is a stupid. It's most likely AfD is a psyop run from within Germany, and why would you use a server within Germany if you want plausible deniability? No news is real
I'm leaning toward believing it because there are nearly zero modern Germans that would stand up for themselves and protect their country from "migrant" invasion
Clown world is jumping the shark
#nevent1q…20wu
The flaming sword is the truth that destroys the illusions we believe is reality
https://nostr.download/e841d3e10ab84d49a5edffebc7afe221bbc231e8d3df1aa2eb36902589e32326.jpg
Cranberry-apple sausages: Crapple
Everyone under 80 has been conditioned to never pick up the phone unless you have arranged a call ahead of time
Imagine we found a way to partition a model so it can be run distributed on separate computers with slow connections, a gigantic ai model that is trained on literally every piece of information everywhere.
Would it solve the knowledge problem of the market? The answer is no. Why?
You are buying the frame, and the frame is completely wrong
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?
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/
If you ask for my email, you also get my npub
"npub1kg4sdvz3l4fr99n2jdz2vdxe2mpacva87hkdetv76ywacsfq5leqquw5te@uid.ovh "
Private aliases were never migrated to the new bridge architecture. Thank you for this precious information, it's now resolved.
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.
Nice spec from @nprofile…9x4s
https://openspecs.uid.ovh/spec/npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr/image-proxy-list
Here is a documentation to self host a bridge https://nostrmail.org/self-host
Does the server responded or it is an empty screen ?
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
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.
I used to like the sidebar.
I like this nip, it's save one request and remove ambiguity. Sadly, almost nobody implements it.
https://openspecs.uid.ovh/spec/npub19vumfllx9yeal9cwrymxcgkpuzf0j5lc8l876a2wpuzdtga5t8usdm3xgr/nip-67
It's quite surprising that Khatru doesn't do NIP-09 deletion properly. It deletes the event when the request comes in, but it also lets anyone republish the deleted event?!
Yes but DM's UI are great for DMs, emails need an other UI
Use a VPN while using a Nostr app, or you will leak your IP address frequently.
How this issue impact you ?
Hello, how did you login on uid.ovh ?
Banking apps that cannot be installed
Notifications from almost all apps
You just have to run a docker compose and your scheduler dvm is up.
Requiring the user to have an always on nip46 signer is a bad choice. Almost nobody have this and even if they have it, they are probably nerds enough to run a scheduler DVM.
Today I tried #appwrite to detach from #firebase but I noticed that it was bad choice.
Appwrite comes with traefik so you need 2 ports dedicated to it even if you have already a proxy like #caddy installed.
By default the cloud functions are only executable if you set a specific header. The other solution is to configure a domain dedicated for the functions and change the name servers to appwrite.io own DNS servers.
Note to self: use Appwrite only if I have a server and a domain exclusively for it.
#nostrhub got updated, nice to see 👍
Hello, it was a mistake in the proxy, thanks for reporting. Also, I'm switching to host only one relay, every url are pointing to wss://relay.nmail.li
Don't you use docker? I think docker is pretty safe.
Of course independent hardware is always better but it also cost more.
I will share you my research:
First, the OG Shipyard DVM, seems buggy and no longer maintened
Second, the recent @nprofile…zmkd DVM, looks good but complex and do not support every kinds, not generic enough
Third, mine, a scheduler DVM generic that work with any event and protect metadata.
https://nostrhub.io/naddr1qvzqqqrcvypzpv3tq6c9rl2jx2tx4y6y5c6dj4krmse60a0vmjkea5gam3qjpfljqyw8wumn8ghj7mn0wd68ytfsxyh8jcttd95x7mnwv5hxxmmdqqxhxcmgv4j82mr9wgkkgand4wun9n
It's nice to see others people interested in running a bridge. Do you want to run a public bridge?
Hello, you can find a deployment guide here https://github.com/nogringo/nostr-mail-bridge/blob/main/DEPLOYMENT.md
Yes, thank you for sharing this, it's fixed in thr version 0.12.5
Hello, first thanks you for your message, it helps make Nmail better.
You had this questions because the uid.ovh bridge has a bug that allow anyone to send as anyone. It's now fixed.
Actually, you can create any identity you want but the new identity may not work.
If you want to use whatever@uid.ovh, people needs a way to resolve your npub. Either your npub is inside your address either people needs to as the bridge (uid.ovh) to resolve it. So an address can resolve to only one npub.
What you have to do, go on the uid.ovh website and claim the address that you want, then you will be able to send and receive from it.
@nprofile…fdn9 is https://app.nostrthreads.com/ open source ?
What are you using to schedule events ?
You can find the nips on github or on nostrhub
https://github.com/nogringo/nostr-mail/tree/main/nostrhub
Pas forcement, avec nostrmail tu ajoutes un moyen supplémentaire de prouver que tu es le propriétaire de l'adresse. Si un bridge to censure/block, tes contacts ont toujours un moyen pour te recontacter. En plus 100% de test données sont sur tes relais donc il est presque impossible de perdre tes contacts ou emails.
La ou tu as raison, c'est que pour profiter du chiffrement de bout en bout il faut forcement etre entre utilisateurs nostr.