Talk to a human.
One inbox, read by the person who wrote the code. No ticket numbers, no triage bot — send something useful, get a real reply.
$ ssh [email protected]
$
pick a subject
Something broke? Send the tool, the shape of the input, and your browser — reproducible bugs jump the queue.
Useful, client-side, no data needed? Then it belongs here. Most of the roadmap started as one line.
[SECURITY] in the subject, redacted examples only — never live secrets. The fix ships before any write-up.
Also valid. Corrections, questions, or a note that a tool saved your afternoon — everything gets read.
after you hit send
What happens next
Every message is read by the person who wrote the code — no autoresponder, no triage bot deciding if you're worth answering, and no mailing list your address gets added to.
- ≤48h avg reply
- 1 human
- 0 bots
- 0 newsletters
quick answers
Before you write
Do you keep what I paste into the tools?
No — the tools run entirely in your browser and nothing is transmitted or stored. If you email me, your message is kept only as long as the conversation needs it, and it is never added to any list.
How do I report a security issue?
Email [email protected] with [SECURITY] in the subject line. Describe the issue with a redacted example — never paste live secrets. You'll get a reply, and the fix ships before any public credit or write-up.
Will you build a tool I suggest?
Quite possibly, if it passes three tests: genuinely useful, fully client-side, and not dependent on your data. Most of the roadmap started as one-line suggestions from readers.
Is there a newsletter or mailing list?
No, and there never will be. New tools and posts are published on the site itself — bookmark it, or let your RSS reader do the checking. Your inbox stays yours.