Mornin', catching up on things!

It looks like there are a few different kinds at play here with the POP Card listings (and shares). The cards themselves use a custom kind 30402 event, but their public listings use a kind 30023 (long-form content) event.

For example, this listing:

https://nostr-react-starter-iysi.shakespeare.to/art/naddr1qvzqqqr4gupzqsa64uxz3ek0kx2mzlhqs0seavay4l06c4xek6a0zup8pmge8c6vqqwxzun5wahhy6edxymn2vekxgenyd3nxymnqttwx3jrzdnhpx56z5

The `naddr` translates to:

```

{

"pubkey": "43baaf0c28e6cfb195b17ee083e19eb3a4afdfac54d9b6baf170270ed193e34c",

"kind": 30023,

"identifier": "artwork-1753623263170-n4d16w"

}

```

The more ideal behavior would be for the site to render your custom kind 30402 event directly, and only create only that event on publish for your listing. As for how to phrase that request via a prompt, something akin to:

"This site publishes artwork as kind 30023 events and uses that event in the /art/naddr... url. This is wrong - the site should instead only publish the kind 30402 when creating new art cards and render the kind 30402 event directly on the page instead of wrapping it in a kind 30023 post. It should also only use the kind 30402 in the /art/naddr... url pattern, rather than kind 30023."

I've had to do something vaguely similar in the past (swapping events used by the application), and had success with this approach. Let me know if there is any difficulty with executing on this though.

https://github.com/nostrability/nostrability/issues/221

cc nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p