cmd

I have realized that there is currently no easy way to check if an existing method supports a new parameter, so that I can fall-back to a polyfill if needed....

I am working on something similar with encrypted event channels. Basically you can use a shared key (and tag hint) to establish e2e encrypted channels. The format I use is...

Looks great. Is this the place to discuss both nips, or are there dedicated discussions for each NIP?

> These articles are meant to be editable, so they should make use of the replace-ability feature of NIP-33 and include a "d" tag with an identifier for the article....

> Also I am not sure of how one of these articles can reference another using the `nref` stuff. That part is broken in the NIP because I got confused...

IME, encrypted group chat is a rabbit-hole of complexity. A lot of folks use double ratcheting as a standard. All the requirements are found in WebCrypto: https://en.wikipedia.org//wiki/Double_Ratchet_Algorithm I have seen...

What about a replaceable event that simply provides each member with the latest shared secret for a channel, encrypted to their pubkey? If you are a member on the list,...

> Pretty much this is what is being done in this NIP 38, where the single shared secret is being shared using kind 104, which is encrypted to the recipeients...

Is it something like this: ## Both Parties ```ts // Generate keypair for channel owner and channel member. const { ownerPubKey, ownerPrivKey } = KeyPair.generate(32) const { memberPubKey, memberPrivKey }...

> NB I am assuming kind 4 works like this ECDH logic you mentioned, without verifying. Because kind 104 follows just how kind 4 does. Yeah you are correct, ECDH...