LNURL of user metadata not updating correctly? #234

Closed
opened 2025-02-25 21:27:51 +00:00 by freakoverse · 1 comment
Owner

not sure if it's an issue, but it doesn't seem like the tip button is picking up the new LN address from the admin npub (it's still using the old address i think, which is degmods@lifpay.me , instead of the new one that I updated in my nostr metadata which is degmods@coinos.io)

i think this is a general issue on the site, where it's not updating lnurl of users as fast as it needs to (caching / not updating? if so, this needs to always be checked)

not sure if it's an issue, but it doesn't seem like the tip button is picking up the new LN address from the admin npub (it's still using the old address i think, which is degmods@lifpay.me , instead of the new one that I updated in my nostr metadata which is degmods@coinos.io) i think this is a general issue on the site, where it's not updating lnurl of users as fast as it needs to (caching / not updating? if so, this needs to always be checked)
freakoverse added the
Kind/Bug
Priority
High
labels 2025-02-25 21:27:51 +00:00
freakoverse added this to the Issues project 2025-02-25 21:27:51 +00:00
freakoverse moved this to To Do in Issues on 2025-02-25 21:27:55 +00:00
Collaborator

Yep, same issue, we are still waiting for fix at https://github.com/nostr-dev-kit/ndk/pull/304.
The created_at is overwritten when saving profile event (breaks comparison for which profile update event is "newer") and it never gets updated with the new values. Prepared the PR which skips the cache for now, once that 304 is closed or cache fixed on their end we can make another change and start using cache again.

Yep, same issue, we are still waiting for fix at https://github.com/nostr-dev-kit/ndk/pull/304. The `created_at` is overwritten when saving profile event (breaks comparison for which profile update event is "newer") and it never gets updated with the new values. Prepared the PR which skips the cache for now, once that 304 is closed or cache fixed on their end we can make another change and start using cache again.
enes closed this issue 2025-02-27 19:13:59 +00:00
enes moved this to In Progress in Issues on 2025-02-27 19:14:16 +00:00
enes moved this to Done in Issues on 2025-02-27 19:15:29 +00:00
Sign in to join this conversation.
No description provided.