Ask HN: What are you working on? (May 2026)
511–520 of 1001 posts
Re: Ask HN: What are you working on? (May 2026)
#512I use it every morning for about 15 minutes. Review the cards, then 1 problem in the algorithms, 1 problem in concurrency, and I'm done.
I wrote more here about my motivations for creating it: https://medium.com/@andreiboar/algotutor-using-ai-to-actuall...
Re: Ask HN: What are you working on? (May 2026)
#513Re: Ask HN: What are you working on? (May 2026)
#514Re: Ask HN: What are you working on? (May 2026)
#515Re: Ask HN: What are you working on? (May 2026)
#516Its a message definition and protocol, addresses look like @user@domain, anyone can run a host, and threaded messages are linked by cryptographic parent hashes..
The idea is to take the best from email: open protocol, domain ownership, interoperability (unsolicited mail is a feature not a bug), and the best from closed instant messaging rebuilt: efficient binary messages, conversational threads, sender verification, message integrity etc. built-in. Originally envisaged for human-to-human messaging but partculalrly interesting time right now with human-to-agent and agent-to-agent messaging...
The OSS stack is up and running: Go host, Dockerised full setup, CLI, Web API, and a spec nearing v1.0. Did Show HN post week ago: https://markmnl.github.io/fmsg/show-hn.html
Seeking feedback, criticism, validation :) protocol bikeshedding, and especially interest from founding-engineer types who want to help build an open messaging ecosystem rather than another closed app..
Re: Ask HN: What are you working on? (May 2026)
#517SDocs is cli (`sdoc file.md`) -> instantly rendered Markdown file in the browser
When you install the cli it gives you the option to add a note in your base agent file (`~/.claude/CLAUDE.md`, etc.). This means every agent chat knows about SDocs and you can say “sdoc me the plan when you’re done with it” and the file will pop open instead of you having to find that terminal session to know it’s done.
Going browser first means you’re not required to install anything to get a great experience.
Despite being in the browser, the content of SDocs rendered Markdown files remain entirely local to you. SDoc urls contain your markdown document's content in compressed base64 in the url fragment (the bit after the `#`):
https://sdocs.dev/#md=GzcFAMT...(this is the contents of your document)...
The url fragment is never sent to the server (see https://developer.mozilla.org/en-US/docs/Web/URI/Reference/F...: "The fragment is not sent to the server when the URI is requested; it is processed by the client").
The sdocs.dev webapp is purely a client side decoding and rendering engine for the content stored in the url fragment.
This also means you can share your .md files privately by sharing the url.
Re: Ask HN: What are you working on? (May 2026)
#518Re: Ask HN: What are you working on? (May 2026)
#519Re: Ask HN: What are you working on? (May 2026)
#520React + TypeScript with Vercel handling deploys, no backend (yet), the puzzles are just JSON. The toughest part is the puzzle generation: packing multiple snaking paths onto a grid like jigsaw pieces with the constraint that each answer has exactly one valid path. Coming up with good two-word themes has been its own challenge too!
Always looking for feedback or suggestions for improvement. :)