Hello nostr:nprofile1qyd8wumn8ghj7mn0wd68ytn5dpjhxctdv43kzapwd9hj7qgewaehxw309aex2mrp0yhx6mmddaehgu3wwp5ku6e0qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qyf8wumn8ghj7mn0wd68yat99e3k7mf0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qguwaehxw309aekzar9d3kxjar99e585unyxy6rjtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz992jelr6 . I am looking at blossom's spec. I have a few questions that I can't make sense of. 

1- Why doesn't blossom use NIP98 as an authorization event? 

2 - Why does it use its own event with kind 24242 that is not in the standard?

3- Why a whole new protocol if it could have been integrated, for example, in NDK + nostr-tools + NIP96?  Does it make sense to go against all the work done these years?

I would like to have a productive conversation, as I am evaluating the possible implementation of blossom for the new version of nostrcheck-server. Starting from NIP96, the modifications to be made in the source code are minimal, apart from the authorization event that does change completely.