hzrd149's avatar
hzrd149
_@hzrd149.com
npub1ye5p...knpr
JavaScript developer working on some nostr stuff - noStrudel https://nostrudel.ninja - Blossom https://github.com/hzrd149/blossom - Applesauce https://hzrd149.github.io/applesauce
hzrd149's avatar
hzrd149 3 months ago
I finally understand MoQ, its just RxJS over QUIC and with a relay in the middle...
hzrd149's avatar
hzrd149 3 months ago
50% success rate on uploading 6 RHR episodes to the new deno blossom-server that is running on a 1 CPU and 1Gb server. very slow but considering just one of these uploads would kill the old server I'm very happy with this. image Not sure what the authentication errors are from yet, technically the server handled all 6 uploads fine. but I guess there is a bug somewhere with long running uploads... Source code:
hzrd149's avatar
hzrd149 3 months ago
Wake up, make coffee, get excited about new Nostr client... Get completely blocked by NIP-42 authentication and decryption requests... Guess I'll just go back to noStrudel and Grimoire that respect my ability to say "no"
hzrd149's avatar
hzrd149 3 months ago
Read this article on a whim... And one question. Are opinion writers paid to be dense?... Half the article is spent rightly making fun of legislators on the absurdity of OS level age verification. But then the writer goes on to say "These kinds of laws don't work. They've never worked. Prohibition failed in the United States." Failed? Yes if you consider that it failed to ban alcohol in the states, but was a great success for introducing liquor licenses and other licensing bureaucracy. This is an opinion piece, the least the writer could do is read between the lines a little and see where this is going. Anyways, it's just frustrating when I read articles about X or Y law nowadays and they all conclude with "this will never work because..." and completely failing to imagine that law X is never supposed to work, its supposed to change culture. View quoted note → Also no criticism twards inpc, I'm just quoting the note because it's easier.
hzrd149's avatar
hzrd149 3 months ago
This was fun to work on and also helped me test some ideas about more efficient event loading in applesauce. Also looking for more Nostr "issues" that could be tested for and added to the report View quoted note →
hzrd149's avatar
hzrd149 3 months ago
Fully reactive NIP-66 monitor UI for checking inbox / outbox status. The "view" is written by composing RxJS streams and returning a stream of "state" that the react UI renders. so there isn't any useState or useEffect in the react UI, everything is handled in RxJS. This means that once I build the state stream, the agent can easily vibe code a UI on top of it to modify the inputs and then render the outputs, no messy state in the UI components image
hzrd149's avatar
hzrd149 3 months ago
Merged BUD-11 for #blossom which moves all the authorization logic and requirements into a single BUD There isn't any breaking changes for clients or server, but it does add a new `server` tag to the kind 24242 event that allows clients to scope authorization events to specific relays Thanks to @Pip the WoT guy for all the help
hzrd149's avatar
hzrd149 3 months ago
Looking for thoughts and feedback on this vibe coded library I'm probably going to use it as a way to learn rust, but the idea is to adapt the stateless relay connection pattern that applesauce-relay defined to rust. The goal is for the app to be able to open a REQ on a relay and not care if its connected, then when the REQ is closed / dropped the relay should be closed behind the scenes