I guess I form an nevent from the event that I don't understand... and I don't ever need to use the other ones.
My app has special kinds for freelance Ticket(32767) and Freelance Offer(32768). A nip89 handler would only be meaningful for naddr. In this case: ```https://satshoot.com/<naddr>```
Oh right. I could do naddr too. I think npub, nprofile, and note (I would use nevent instead) don't need app handlers so I'll just do nevent if not replaceable and naddr if replaceable.
The idea behind putting handlers with nprofile and such might be that there are clients that don't render profile metadata(rarer case perhaps) or even kind1s like in my case. My app creates a feed of freelance tickets instead of a kind1 feed. However, I could implement mechanics to jump to a different client to render kind1s under certain conditions or an iframe to render any event that references my freelance ticket/offer. Not sure, just thinking out loud.