Been getting this a lot lately..even on npubs that I have zapped numerous times..sometimes if I wait a while and try again it works (a loading issue I guess).
Sometimes no amount of waiting helps.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
#amethyst
#zaps
#asknostr
Ditto. For last 2 hours for me.
Same here..maybe some relay issue?
I assume it must be, but I can't identify which or why. I also have the issue that many npubs don't load completely and just stay as stock (robot) picture and npub string rather than nip05
Well what the frog.
Me too.
Got that msg just now when i tried to zap you.
Were trying to zap Vlady? If that is the case, it's probably because the app is still loading his profile. I will see if I can increase the priority of that task to load them faster.
In that screenshot I was actually trying to zap nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w and his comment and npub were fully loaded as far as I could tell, though it usually happens on npubs that are not fully loaded so in general that does seem to be the issue.
Npubs have been taking way longer to load lately. Sometimes if I click on their profile and then go back it will then finally load and allow me to zap, but that tactic is hit or miss.
Hum... thank you for the report. I will investigate it. Maybe we broke something in the latest versions.
It looks like nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpr9mhxue69uhhyetvv9ujumn0wd68yanfv4mjucm0d5q3samnwvaz7tmsw43xc6tr9eex2mrp095kueewd9hsfz6x6a doesn't have a lighting address setup. I've checked in multiple clients.
This was happening to me yesterday, but it was only happening with people that had WoS addresses so I thought it was a WoS issue.
