Thanks, I will check them out. I don't use many "web apps", just Coracle for view only with my public key and cashu.me. I use Gossip desktop Nostr app for Linux which allows me to keep my secret key localky and secure. But the concept with message signing is very interesting.
Logil everywhere by signing a message. this is what makes nostr auth simpler and better than google.
Do you mean just sing a message with the secret key without revealing it? That would be perfect but where is this implemented? Most apps require you to reveal your secret keys and to trust them ...
Linux is getting smarter every day.
https://video.nostr.build/a06b551c14ae00381217ed61d0f19062d1f3ea81e9653b9441810caf358cf137.mp4
Its an interesting attack, same as in email protocol. For now muting works. I guess spamlists from trusted parties will be one of the solutions for the future mixed with some sorts of filters ...
Wow, a good-hearted thief? Didn't want to cause pain with documents and communication, just to steal something thats not that relevant ... interesting mindset.
If you two collaborate I am sure it will become global bestseller. Absolutely seriusly. And probably you will both enjoy it : ))
Are you posting from the kindergarten?
I have tatested #Nostr Freedom and it tastes delicious too. I already see they match really well together.
#Bitcoin-ers don't trust, they verify. So it does not matter if someone dines with Jesus too.
Line is still there under different question https://t.co/yTJRrTuexD
nostr:nevent1qqs8lv476ggexl5mtuvhwyar5ejdn0msaruscd342zr45n559cjg9lchwl5g8
All of my friends know about #Bitcoin. 1% are paying attention and own some. From the rest, some are curious, some still skeptical, some bullish but don't own ... I guess they will start paying attention when #Bitcoin Moons, then will get small amounts at the price they deserve but many will be left behind. And #Bitcoin will definitely penetrate hard the world economy, its the perfect medium for it, the Perfect Money.
Its time for #Bitcoin Global Reserve Money 🧡⚡️🫒
- no one controls it
- peer-to-peer, no intermediate
- no one can stop it, freeze it, seize it
- 21M limited supply
- perfect for big international transactions
- perfect for small #Lightning fast transactions as well via #LightningNetwork and Ecash / Zaps
- perfect store of value
- Worlds Freedom Money
- Hope for Humanity 🧡
Cheers. I use it and find it really nice (for Zaps and small amounts of course, its not self-custody). If you have questions I may be able to help. But its quite easy to set up even without RTFM : )
https://wallet.cashu.me/ works perfectly with min https://mint.minibits.cash/Bitcoin
Or a Papusa from El Salvador. I just got a ham and cheese toast, delicious.
Yes, a statistics will be needed but simple average of response times and uptime against the relays can be a pointer.
2 fast, stable, robust ones - can be choosen randomly from a list of fast, stable, robust ones
1 random from the not so fast, not so stable ones
or something similar
Some thoughts *before* I read the draft NIP.
I think we should propose an #MLS cipher suite that uses secp256k1 and reserve an identifier for it. That way we it can use libsecp256k1.
The secp256k1 curve can be used for both key exchange (xonly?) and (BIP340 schnorr) signatures. This curve is not yet listed under the recommended MLS Cipher Suites.
By carefully picking the other parameters it may be easier for Bitcoin signing devices to keep your chats ultra secure. And if a nostr client is already using some Bitcoin related library, then it's great if it already has the required ciphers.
Meanwhile rfc9420 has a mandatory-to-implement cipher suite MLS_128_DHKEMX25519_AES128GCM_SHA256_Ed25519. This is useful for interoperability with other social networks, but that seems low priority to me compared to being simple to implement. And with respect to not adding more dependencies and not increasing the attack surface of cryptographic implementation errors.
MLS supports switching ciphers for existing groups, so we can always add compatibility later. Or secp256k1-pill the other networks :-)
For the hash function sha256 makes the most sense.
For AEAD ChaCha20Poly1305 is used in BIP324 (encrypted p2p transport) as well as the Stratum v2 noise protocol.
Not sure what to pick for the Key Encapsulation Mechanism (KEM), or maybe that's already covered by ChaCha20Poly1305?
So CipherSuite name MLS_256_???_CHACHA20POLY1305_SHA256_Secp256k1.
https://www.rfc-editor.org/rfc/rfc9420.html#mls-cipher-suites
Sounds very good.