I will be honest. The hard part of Deckhand was not the WebSocket protocol, nor the sandboxed iframes, nor the Go binary that runs everywhere. The hard part starts now, and it is not something I can code.
A tool like this lives or dies on one thing: people using it and saying so. Not stars for the sake of stars. Real talks, real rooms, real "it broke here" messages.
What would help, in order
- Try it on your next talk.
brew install stranix79/tap/deckhand,deckhand present your-folder/, scan the QR with your phone. Ten minutes. If your slides are not HTML yet, this prompt gets you a deck from any language model. - Tell me what broke, or what confused you. An issue on GitHub, a mail, a message. The remote on a phone you own, the deck format, the hub: I have only tested my own setup, and I know it.
- Share it with one person who presents. A colleague who does the Monday demo, a teacher, the friend who organises the meetup. One message from you is worth more than any launch post I could write.
- Star the repo if you like the idea. It is the signal other people read first.
- If it saves you a talk, there is a sponsor button. No pressure. The binary stays free and MIT either way.
What I commit to
- Every issue gets an answer within a few days, and a fix or a clear "no" within a reasonable time.
- No account for the local mode, ever. No telemetry in the binary, ever.
- The hub stays self-hostable, with the compose file in the repo.
- The newsletter only carries releases and nothing else, one address and that is it.
That is the deal. Try it, break it, tell me. Thank you.