Maybe you’re just going about it the wrong way? Instead of trying to get every client to implement at the same time, why not try a strategic partnership to prove the concept of why #NIP42 is so powerful. Work with one client and one content creator to showcase the benefits. If it works, then others will follow. If #NIP42 will enable what you’re saying it will, then I’d fully support it and expect my client to implement it.
Discussion
NIP-42 is not theoretical or conceptual, it’s a merged NIP with a spec. It’s not speculation for me to say what it enables.
We’ve already built NIP-42 optionally in to one of our relays and it works on Coracle, the only client that I know of that has a working NIP-42 implementation.
Nobody is able to put any of these features in to practice unless some critical mass of clients support it. I’m not trying to get “every” client to implement it, I’m trying to get the most popular clients to implement it so that it can be used on the network.
If one client of the top clients implements it ahead of the others, we will absolutely provide them with extra support and try to showcase the use case on their client. I don’t understand why casting a smaller net (1) would be better than a bigger one (4) in this context?
Well… it seems like casting a wide net has been ineffective until this point if no one is implementing it. Im curious why if it has such a powerful use case, it’s not getting used. Just my 2sats, not trying to argue with you.
Elsat and I just posted these last night so the fact that one of them is already being worked on is definitely progress. Nobody has been advocating for NIP-42 from the developer side even though users ask for features that requires it everyday (without knowing what NIP is needed). I am now that advocate.
