nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft should we also leverage the current kind 0+3 as a (loose) WoT for NIP-89?

The reason I'm asking because its probably an additional barrier/complexity for apps to adopt the (exact) WoT version (31989+31990)

Applications usually already have kind 0 profiles, we can put the handler tags in there instead of in kind 31990 (Handler information).

People also already follow application profiles, this would replace kind 31989 (Recommendation event).

Compare right now stemstr recommended by (exact):
https://nostur.com/screenshots/stemstr-exact-wot.png

vs Stemstr followed by (loose):
https://nostur.com/screenshots/stemstr-loose-wot.png

cc: nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn (don't know who else has integrated NIP-89)