Preach it baby!!!!

yo yo nostriches!!! Is there anyone out there who cares enough about NIP-98 for a chat? I'm using it for api access. The client signs an event (which is never published but sent in the Auth header as per the NIP). The server validates the event and then returns the records associated with the signer. The issue is when my nip07signer (Flamingo) prompts me to sign the request, it is blank. This is because the content field SHOULD be blank according to the NIP. The thing I want to do is change the NIP to MUST have content which contains the METHOD and URL strings to be valid. This would mean that the user sees what they are signing and validation can do a simple string search of the content field based on the url and method tags. Anyone got any ideas on this? Also, if you know of anyone other than (the likely far to busy for banter about draft|optional NIPs) @fiatjaf, with the time and knowledge to give feedback on this idea, please tag them in for me :)