Applesauce pyramid relay https://relay.applesauce.build/
Not sure exactly what I'm going to do with it but maybe we can build a simple Q&A forum using NIP-29 for applesauce div stuff

Not a bad idea. although NIP-65 should stay the way it is and the users client should be responsible for updating to the latest "relay pack" they are following

deno SSR experiment https://github.com/hzrd149/fresh-nostr-relay-explorer
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.

@nevent1qvz...

So far, I'm very impressed with https://fresh.deno.dev/
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.

You can also use an AsyncEventStore that is backed by a database but that's more for backend apps and wouldn't work very well with UI components https://applesauce.build/storage/databases/

Caching is handled when the app loads events. So the applesauce-loaders package has a much of "loader" methods that all accept a method to read from a cache. Then for saving too cache that can be handled by subscribing to the event store and saving new events to the cache
https://applesauce.build/storage/caching

The EventStore is in-memory only. It's designed to be the state that the UI components read from

I've been using cursor and ill probably keep using it for most things. but going to start venturing into vibe coding, specifically not looking at the code.

http://applesauce.build/ is live

It worked. OpenCode is awesome
@nevent1qvz...

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
@nevent1qgs...