#realy #devstr #progressreport
just been tidying up in preparation for implementing the simplified nostr protocol spec https://github.com/mleku/realy?tab=readme-ov-file#simplified-nostr
found a few things that were not properly dealt with, mainly related to the new public readable option, and the request filtering
important change now in v1.9.5 (current at this time) is that it now correctly is refusing to process queries for DMs and Application Specific Data and related privileged event kinds with no auth
there is already one working path endpoint, `/relayinfo` which i haven't documented yet, it's just the same as nip-11, but specific to the new protocol, because it's on a path
one key thing that will be happening even with subscription based websockets APIs is that they will do auth using nip-98 at the request level, and the `/capabilities` endpoint will specify if an API requires auth or not, or such finer details like "for kinds a, b, c" as it will for the filter endpoint on privileged events as i was talking about just above
ok, getting to it
there will be a full, sane http RESTful API put together soon, which will be very nice for resource constrained devices that can't do websockets, mainly this is going to mean #alexandria can be deployed to read books on an ebook reader
but i think that general adoption of this protocol extension should take place anyway, because it so greatly simplifies implementation for the majority of types of queries and publication requests that clients use, meaning nostr-noob devs will be able to get something working sooner
well, at least for #realy anyway y'alls other peoples gonna have to catch up at that point
Showing page 1 of
1 pages
