well, i don't think it really solves any problem tbh

yes i read through the NIP and it's overly complicated considering it's just a proxy protocol

i remember actually suggesting the idea not long ago that NIP-42 auth should use encryption known only to the recipient and vice versa, which would enable proxying the signatures, and then i read today, i mean, i can't spend all my time reading all these things - that the content of NIP-46 messages are NIP-4 encrypted messages. well, duh, but funny in a way as well

i think nostr suffers from too many elements where two or more domains are jammed together into one protocol, tags on events, for example, and how many other NIPs involve using NIP-4, which is supposedly deprecated? for which use? DMs only, but NIP-46 apparently not

typical beginner architectural mistakes, mixing up features into one section and then when it turns out that is inconvenient, no way to separate them, and/or nobody adopts the isolated version because integrated version exists, which should never have been there in the first place 

 You may or may not be right, my point is that nsecbunker doesn't need any tunnels and can work on your phone. 

 ephemeral events that have to be held for an indeterminate amount of time is not in the definition of ephemeral 

 anyhow, i haven't read the nip that close, but i just wonder why so much more energy goes to it than NIP-42 which actually solves an immediate problem for relays, i think we should have both working, for sure, but i don't know whether this is overly complicated because i had to scroll through three screenfuls of text which seems like a lot of stuff for a simple proxy process 

 and upon a reread, it really does jam way too many things together

i don't think that bitcoin would have ever been built without none of this, it's only been the post-established-working-protocol that this has been adopted

this specification process should be a wiki

you know, like that thing you been working on @PABLOF7z  

 if you think nip 42 needs more energy, then contribute to it. it's not up to you to decide who works on what. 

 the spec is fine

it's the lack of implementation, and how much of an impediment that is to real business use of this protocol 

 do you feel dumber after this interaction Pablo?  i did. 

 HAHAHAHAAA