Its not complete but I'm very happy with it. super easy to render on the server and then ship live components to the client only when needed.
View quoted note →
I built a SSR react app with data that was fetched on the server side and a live client feed and didn't have to fight the compiler at all. It's concept of islands make it very easy to understand what code is run on the server and what code is run on the client.
A vibe coded user script to block all NIP-42 signing requests except for a whitelist of relays. I don't have time to write my own signer and I'm getting tired of fighting the constant authentication requests for 100s of relays whenever I use any nostr client
View quoted note →
Nuked my follow list then found and fixed the bug in applesauce. luckily I was able to find an older version and restore from that.
Still doesn't feel good though :)
Trying to think of a good domain name for the Applesauce documentation, examples and other stuff to live under. Unfortunately, applesauce.dev is taken.
I'd like to set up a simple relay, maybe with some NIP-29 groups, and see if it's possible to build a community around applesauce development and apps that use it. But first I need a domain.
The idea is to have an "implementations" folder that contains documents describing various things that can be done with the blossom spec but do not change the spec itself
does not support a "mpv:" or "video:" link format. I want to be able to add a generic "open in local video player" link to noStrudel so I don't have to keep the browser open
to check notifications is awesome. client loads quickly (unlike noStrudel 😞) and only loads the events I want to see.
Also the way @verbiricha implemented NIP-42 auth means that I'm not annoyed by signing requests while I'm using the app
If you want to test it try opening this spellbook View article →