do you think it would be a bad idea to include the nip7 type declared in nostr-tools? I mean, with no js, just the interface, so we dev could declare in the browser environment manually, like this:
https://m.primal.net/IJPZ.png
When I need nip07 I put a nip07 interface locally in each application
https://m.primal.net/IJPX.png
Yes, I think it's a very good idea.
What about having an actual module called nip07 with actual functions in it, just calling window.nostr on the back?
As far as I understand the real implementation in javascript is injected by the extension, am I wrong? But they cannot provide the typescript interface
If it had a proper solution to races then yes please!
You know I'm something of a racist myself.
I got it, you mean to create an exportable nip7 non related to window but that talks to the window.nostr, that's it?
I think the interface is enought to me.
Can I open an issue about this in nostr-tools?