SondreB

Nostr Connect: Uses Remote Signer Identity instead of Client Identity

3

I'm doing some testing with noStrudel and a new remote signer I'm developing and from what I can see, noStrudle takes the public key from bunker:// URL or the pubkey...

The NIP-46 specifies the use of NIP-44 encryption scheme, but noStrudel is using NIP-4. Maybe it is not explict, but at least the examples use that: https://github.com/nostr-protocol/nips/blob/master/46.md

https://nostrdesign.org/docs/how-to/private-key-safeguarding/#preventing-accidental-pasting

Remove usage of content for relays on kind 3 (Contacts)

1

Previously there was non-standard implementations across Nostr clients to use `content` on the kind 3 event to store relays. This task is to track the removal of this functionality and...

Implement a generic file manager that implements the NIP-96: https://github.com/nostr-protocol/nips/blob/master/96.md

A few quick questions and feedback

9

What is the rational to have patching action? Wouldn't it be enough to just update the whole DID on updates? - Should relays validate updates to DIDs? - Clients need...

The NIP-46 specifies only NIP-44 as valid encryption method, not NIP-4, which is the default in this library. The `connectToRemote` should default to NIP-44, not NIP-4 like now. Need to...

Don't know if this is specific to Azure Web Apps for Containers (usually works fine with ENV variables), but when attempting to set the config file using the ENV variable...

## Describe the bug There is an account I came across that contains a newline character right before " (end of value), and that does not parse with JSON.parse(). ###...

The `parseConnectionString` function returns only the first relay, yet the specification allows specifying multiple relays, so perhaps this should be changed to return array of relays? I don't know the...