- Outline the setup and how I'd like to deploy it, what I wanted from it and how users would connect (I'll drop the initial prompt down the bottom of the post)
- Claude comes back with deep insight into the limitations of the network, the architecture I'm planning and brings up things I hadn't thought of like spam, abuse and network overload considerations
- I ask it to write a detailed spec including all the architecture and components
- The initial spec includes a whole section of unresolved questions which I answer and it finalises the spec.
- I move the spec into a new chat and direct it to build the thing.
- Claude outputs a tar file with the full thing.
- Initial spec in an LLM output to Markdown
- Migrate into Cursor with Linear upstream
- Cursor agents build the app
- Deployments go to Github PRs which are built and test by Cursor agents
- PRs merged manually which builds the production artifacts
- I've used Railway a bit for deployment here
I want to set up a Meshcore bulletin board system that users can access through direct messages. It could provide services such as news headlines, quick weather info, public message boards with persistence and messages to other users that are asynchronous.
The idea would be that messages to and from an individual user would be their unique stream connecting them to the BBS. Authentication would just be their public key used to sign their DMs. If in understanding how DMs work correctly.
How would I get this set up? I'm thinking of running it in a VM on my unraid server with a serial connection to a Meshcore companion device. It could use the Meshcore python library to connect.
https://github.com/meshcore-dev/meshcore_py
Build me an outline of how this would work. Highlight any potential issues or things I haven't thought of.