mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-11-10 14:19:08 -05:00
Remove bare emails
This commit is contained in:
parent
e6c9bf4ea2
commit
5571adc12a
4
05.md
4
05.md
|
@ -58,7 +58,7 @@ A client may implement support for finding users' public keys from _internet ide
|
|||
|
||||
### Clients must always follow public keys, not NIP-05 addresses
|
||||
|
||||
For example, if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying "bob@bob.com" for that user, as that will have become an invalid `"nip05"` property).
|
||||
For example, if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying `bob@bob.com` for that user, as that will have become an invalid `"nip05"` property).
|
||||
|
||||
### Public keys must be in hex format
|
||||
|
||||
|
@ -66,7 +66,7 @@ Keys must be returned in hex format. Keys in NIP-19 `npub` format are only meant
|
|||
|
||||
### User Discovery implementation suggestion
|
||||
|
||||
A client can also use this to allow users to search other profiles. If a client has a search box or something like that, a user may be able to type "bob@example.com" there and the client would recognize that and do the proper queries to obtain a pubkey and suggest that to the user.
|
||||
A client can also use this to allow users to search other profiles. If a client has a search box or something like that, a user may be able to type `bob@example.com` there and the client would recognize that and do the proper queries to obtain a pubkey and suggest that to the user.
|
||||
|
||||
### Showing just the domain as an identifier
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user