Spl0itable
Update to support NIPs listed below
Thanks for the feedback! NIP-42 is on the roadmap. I tried integrating NIP-50 in some earlier iterations and it did not perform as well as I'd had hoped, so I removed support. I believe due to the way events are stored and the limited number of events that we're able to fetch/query. Though, I have some ideas for how to potentially resolve it. Including supporting replaceable events like NIP-65. We'll see how it goes in the future.
Thanks for your response I do hope it gets solved. I look forward to the updates
Is there a roadmap somewhere to track progress? I'm also interested in NIP-42 as well as NIP-26 and would like to help if there is some good way for me to get started.
@tionis At this moment, both NIPs 42 and 50 appear to be unachievable. I had extensively tested both and neither function properly due to the stateless nature of Cloudflare Workers and due to the data structure in R2 bucket.
As for NIP-26, this appears to publish a note that adds tags for the delegation. By default, all tags and REQs for any tag is supported by default on Nosflare. I have not yet tested, but in theory NIP-26 should work already.
Regarding NIPs 42 and 50: that's really unfortunate, they would would really have been nice to have.
NIP-26 would maybe be interesting in combination with authentication, if I understood it correctly.
What exactly blocks NIP-42 (Authentication) I can understand full-text-search being blocked, but why auth?
What exactly blocks NIP-42 (Authentication) I can understand full-text-search being blocked, but why auth?
@tionis due to the stateless nature of Nosflare (since it runs on Workers) each connection to the relay uses a new Worker, which is impossible to track the authentication <challenge-string> for each request.
So, it effectively just writes a bunch of data to the R2 bucket that cannot be retrieved for the same user. It could possibly be solved through IP tracking, but not sure I want the relay implementation to track people.
Since it's FOSS, someone could fork and build that into it if they'd like. But, for now it seems that NIPs 42 and 50 aren't possible with a serverless style relay.
I've reopened this issue as these NIPs can now be included since the relay code has been refactored and updated to utilising a SQL database. I'll investigate including them soon.
All three NIP-42 and NIP-50 and NIP-65 have been added to the latest version