Nostr is so weird. I still receive zaps sometimes on a Lightning address that I haven't been using on my profile for months.

Reply to this note

Please Login to reply.

Discussion

Maybe some people have it stored somehow

Is it all zapvertising?

Off topic, but is anyone shilling ecash to the signal foundation? They need to integrate this instead of the mobile💩coin !

Fully agree and it would be perfect for internal payments like their use case. Wonder what nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m thinks.

Are you sure it's nostr or people who just have your old lightning address and are "zapvertising" or just tipping you with old info they have?

Yep, it's nostr zaps

Same.

This is the thing that I desperately want to fix. Kind 0s should be dead simple to find. I'm open to any ideas for how we solve this, but some deterministic way of finding the latest kind 0 for a particular pubkey would be a game changer. I hate having to query a bunch of different relays for something as simple as a profile picture and display name.

nostr:note1k8cc83ca5y7fa4pmu4m2qg5q7ant5cl97q2n7qyn6t3xmvkzczmqsymng4

This is why AT protocol includes an offline recovery key that can be used to recover your account by signing a redirect from the old to the new online functional key

Same here. Can't figure out why it's happening

Information doesn't propagate everywhere with constant speed

I've also tried to "republish" my profile, aka make changes and save again - didn't help. My guess is that I might have used specific relay in a past that isn't in my list anymore and data doesn't get updated there?

Too many clients or services are caching data

probably a relay didnt get your latest profile update. so it thinks months old profile is still the latest.

Enuts caches old Nostr profiles. I can’t figure out how to update mine.