mleku
mleku
The BIP-340 support is not complete in btcec. It does not accept variable length messages, and it does not contain the extra 4 tests added to it that test this...
I think the reason why there is confusion over the issues of these message propagation styles is the lack of distinction between message types - **Secret** Kind 4, 1059, 1060...
currently there is two fields in the Limitations section relating to limits on access, `auth_required` and `payment_required` neither of these have a secondary distinction of "for publishing events" i propose...
in most dynamic systems, let alone distributed systems, events that delete items from the state tend to be racy, very racy, and for users, losing their profile or relay lists...
currently in the protocol there is no means for the client to request authentication, this means that clients cannot preemptively authenticate when they see authentication required in the NIP-11 since...
maybe time to update the summary text for this repository?
due to the limitations of the http request runtime of javascript in browsers, it is technically correct that JSON is in fact JS code, and thus servers serving up `nostr.json`...
there is a field in the relay information for supported NIPs but none of the stuff in this repo actually say which ones are supported neither do the examples set...
i just tested and with a subcommand and a flag value with the same `-a` the one in the subcommand did not work or register an error not sure if...
this is probably a long term process to actually happen, but this is the reasoning behind why to do this: i am running a local cache relay with this feature...