What gets a fast reply
- A tool that produces the wrong output. Include the exact input if you can share it. Most parser bugs are one specific character in one specific position, and a real example finds it in minutes rather than hours.
- A tool that fails on a valid input. Especially for the YAML, cron, and CSS tools, where the specifications are large and this implementation covers the practical subset rather than every corner.
- A tool you keep searching for. The build list is driven by what people actually need, and a single clear request is usually enough to put something on it.
- Anything privacy-related. If you spot something that contradicts the privacy policy, that goes to the top of the list.
What I cannot help with
I cannot debug your application, recover a file you converted, or tell you what a token you decoded means. The tools keep no history, so once a tab is closed the data is gone from everywhere, including from me.
Please also do not email me live credentials for diagnosis. If a token fails to decode, describing its shape is enough: the algorithm in the header, the approximate length, and what error appeared.
Other ways to reach me
Email is best: nosborne@tessacodesolutions.com
There is no form that posts to a server here, and that is deliberate. The whole site is static with no backend, which is what lets the tools promise that nothing is uploaded. Adding a form endpoint just for this page would undercut the claim, so the composer above hands off to your own mail client instead.
Response time
This is a side project, so allow a few days. Bug reports with a reproducible input get looked at first, because they are the ones I can actually act on.