-
Notifications
You must be signed in to change notification settings - Fork 8
Description
Many clients render the same notes with different event types, for example:
naddr1qq9hq6t60fsj6er0w4nksq3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqp65wec2m30
naddr1qvzqqqr4gupzq0mhp4ja8fmy48zuk5p6uy37vtk8tx9dqdwcxm32sy8nsaa8gkeyqy88wumn8ghj7mn0wvhxcmmv9uqqkurf0faxzttyda6kw6qesya2l
nevent1qqsv2hheuzmjcmkplmhvmnlkuxtq9q30khux2ztqp7te6tenq0gazsspvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33v9jksvn6wu6x2mr9waun2d3cxfk8scek0phxcut6dfh8s6mnwyenqvm8wa6nymnsveshsep589mx6er9xeckxuf5demhs0mzwfhkzerrv9ehg0t5wf6k2q3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqp65wse9xvv
These all point to the same event. The naddr events work when appended to the zap.cooking/r/ URL format but the nevent version does not. We should have a way to convert this event to the proper format to display or support nevent types natively if possible.