For anyone using the `applesauce-relay` package. there is a breaking change coming in v3. The `publish` and authentication methods will return a Promise instead of an Observable. Should make it more intuitive to use for humans and AI since you won't need to wrap everything in `lastValueFrom`

GitHub

Version Packages by github-actions[bot] · Pull Request #24 · hzrd149/applesauce

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be publ...

Everyone: what is 1+1 JavaScript: yes View quoted note →

#noStrudel now supports NIP-17 messages. It took a bit of work for me to implement them In the way that I prefer but now any other client that is built using applesauce can support them in the same way :) View article →

Great breakdown of some clients and the various ways they try to show trust on users profiles View quoted note →

Finally finished all the features for NIP-17 messages in noStrudel and I think I've managed to create the most informative UI of any nostr client, it literally tells the user everything that is happening. although it looks pretty ugly. Next will be to cleanup some stuff and fix any bugs, then release and hope it never has to be worked on again The first flow is using manual decryption and auth The second flow is using automatic decryption and auth

More strange behavior. why would a relay reject a valid authentication response? Isn't the whole point of NIP-42 to just tell the relay who I am? not for the relay to tell me if I have access? View quoted note →

And another strange NIP-42 behavior. inbox.nostr.wine says "auth_required" in NIP-11 but when you connect it dose not send an AUTH challenge until the client tries to publish or read So noStrudel is in a staring contest with the relay because I don't want it to send a REQ until authenticated but the relay wont send the challenge