Ah, so the meshcore is reading ble messages from bitchat?

There is not web UI (yet). its a remote MCP server so it has to be accessed by an AI agent or by running:
npx @modelcontextprotocol/inspector --server-url https://mpc.applesauce.build/mcp

Ill figure out how to build a chat bot UI later :)

Applesauce has an MCP tool now https://jsr.io/@applesauce/mcp
There is a public instance hosted at: https://mcp.applesauce.build/mcp so it should be useable without installing and even inside shakespeare

This started out as a learning project for myself trying to learn how MCP and RAG databases work. its turned out to be pretty useful. I've done a few tests with Claude and it seems to prevent almost all the issues I was having before like bad imports, methods that don't exist, re-writing things, etc. but I don't know how well it guides the agent to building things the "correct" or optimized way.

Anyways, please give it a try and tell me if it works. I'd like to keep optimizing this

Does this require any modifications to meshcore or is all on the bitchat side?

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