NIP-46 server #625

New issue

Closed

opened 2024-01-18 13:58:27 +13:00 by mikedilger · 3 comments

mikedilger commented

2024-01-18 13:58:27 +13:00

(Migrated from github.com)

Serve as a NIP-46 nostr connect server

See https://github.com/nostr-protocol/nips/blob/master/46.md

Presumed method, started on gossip:

User configures gossip NIP-46 with a set of relays
Gossip creates a keypair for itself
Gossip displays a token for the user to post into their client
Gossip listens for 24133 events on that relay to itself and handles them.

Presumed method, started on some client elsewhere:

User posts a nostrconnect url into gossip to configure gossip
Gossip creates a keypair for itself
Gossip sends connect message to the relays found in that nostrconnect URL
Gossip listens for 24133 events on that relay to itself and handles them.

For use of NIP-46 as a client, see #227

Serve as a NIP-46 nostr connect server See https://github.com/nostr-protocol/nips/blob/master/46.md Presumed method, started on gossip: 1. User configures gossip NIP-46 with a set of relays 2. Gossip creates a keypair for itself 3. Gossip displays a token for the user to post into their client 4. Gossip listens for 24133 events on that relay to itself and handles them. Presumed method, started on some client elsewhere: 1. User posts a nostrconnect url into gossip to configure gossip 2. Gossip creates a keypair for itself 3. Gossip sends connect message to the relays found in that nostrconnect URL 4. Gossip listens for 24133 events on that relay to itself and handles them. For use of NIP-46 as a client, see #227

mikedilger commented

2024-01-31 16:07:03 +13:00

(Migrated from github.com)

This was working on unstable at fb24f723ee

But we have a bit further to go:

However, there is no pop-up approval yet. For encrypt/decrypt/sign operations we should popup and ask the user to approve it.
Also, when setting up, the user should select a name so that we can use that name in the list and in the popop to specify which client (rather than the random client pubkey).

This was working on unstable at fb24f723eee557875bba554838d55938b9b10f67 But we have a bit further to go: - [x] However, there is no pop-up approval yet. For encrypt/decrypt/sign operations we should popup and ask the user to approve it. - [x] Also, when setting up, the user should select a name so that we can use that name in the list and in the popop to specify which client (rather than the random client pubkey).

mikedilger commented

2024-03-08 09:18:54 +13:00

(Migrated from github.com)