this is basically sending event kind 0, but nostrweb should also record the latest set_metadata which could've been sent to a different relay.
this is basically sending [event kind 0](https://github.com/nostr-protocol/nips/blob/master/01.md#basic-event-kinds), but nostrweb should also record the latest `set_metadata` which could've been sent to a different relay.
should the profile form data be saved in localStorage?
if the profile should automatically fetch and display kind 0 data from all relays for the pubkey used (in case use updated data on another client)?
changing keys should probably empty the profile form & try to fetch data for the new keys
I think first draft PR is ok-ish.
I'm not sure yet:
- should the profile form data be saved in localStorage?
- if the profile should automatically fetch and display kind 0 data from all relays for the pubkey used (in case use updated data on another client)?
- changing keys should probably empty the profile form & try to fetch data for the new keys
should the profile form data be saved in localStorage?
yes. so that your own posts don't even need to do a round trip for profile metadata - simply grab them from the localstorage
if the profile should automatically fetch and display kind 0 data from all relays for the pubkey used (in case use updated data on another client)?
i'd expect it to prefer localstorage whenever available, and start looking for kind 0 otherwise. it's faster and imho makes most sense because as a user i have set to specific values using the very same client (browser), so would expect it to remain exactly the same for as long as i'm using this client.
changing keys should probably empty the profile form & try to fetch data for the new keys
👍
> should the profile form data be saved in localStorage?
yes. so that your own posts don't even need to do a round trip for profile metadata - simply grab them from the localstorage
> if the profile should automatically fetch and display kind 0 data from all relays for the pubkey used (in case use updated data on another client)?
i'd expect it to prefer localstorage whenever available, and start looking for kind 0 otherwise. it's faster and imho makes most sense because as a user i have set to specific values using the very same client (browser), so would expect it to remain exactly the same for as long as i'm using this client.
> changing keys should probably empty the profile form & try to fetch data for the new keys
👍
for what this issue is concerned, i think it's done 👍
the rest in #9 sounds very related but much more than the scope here.
for what this issue is concerned, i think it's done 👍
the rest in https://git.qcode.ch/nostr/nostrweb/issues/9#issuecomment-343 sounds very related but much more than the scope here.
this is basically sending event kind 0, but nostrweb should also record the latest
set_metadatawhich could've been sent to a different relay.I think first draft PR is ok-ish.
I'm not sure yet:
yes. so that your own posts don't even need to do a round trip for profile metadata - simply grab them from the localstorage
i'd expect it to prefer localstorage whenever available, and start looking for kind 0 otherwise. it's faster and imho makes most sense because as a user i have set to specific values using the very same client (browser), so would expect it to remain exactly the same for as long as i'm using this client.
👍
for history, it was
e2431c7e60for what this issue is concerned, i think it's done 👍
the rest in #9 sounds very related but much more than the scope here.