Contact

Email

Write to [email protected] about anything to do with this site.

MyToolery is built and maintained by one independent developer, so replies are written by hand and can take a few days, particularly across time zones. Every message is read.

There is no contact form here on purpose. A form needs a server to receive it, and this site deliberately has no back end that accepts your data - see the privacy page. An address you can write to from your own mail client is more honest than a form that pretends to be something it is not.

Reporting a wrong result

This is the most valuable thing you can send, and it is worth interrupting whatever else is in the queue. A tool that quietly returns the wrong answer is worse than one that is missing, because you have no reason to doubt it.

What makes a report quick to act on: which tool, which language you were viewing it in, what you put in, what came out, and what you expected instead. The browser and version help when the cause turns out to be a platform difference, which for date, encoding and clipboard behaviour it often is.

If the input that triggers the bug is something you cannot share, a description of its shape is usually enough - "a JSON object about 4 MB with deeply nested arrays" narrows it down without you sending anything at all.

Suggesting a tool

Requests are welcome. The ones that get built tend to be small, single-purpose, and possible entirely inside a browser, since nothing here sends your input to a server.

It helps to say what you are currently using instead and what is wrong with it. "There is no good X" is a much stronger case than a bare name, and it usually describes the thing that would make a new page worth visiting.

Some things cannot be built under this constraint at all - a DNS lookup or fetching a remote certificate genuinely needs a server. Those get declined rather than implemented in a way that would break the privacy promise, and you will get a straight answer about which category a request falls into.

Corrections and translations

MyToolery is published in seven languages, and the content in each is written rather than machine-translated. That does not make it correct.

If a description reads awkwardly in your language, uses a term no developer actually says, or is simply wrong, please say so - and please do not soften it. Wording that sounds slightly off to a native speaker is invisible from the inside, and hearing about it is far better than not.

The same goes for the technical content in any language: if an explanation of an algorithm, a standard or an edge case is inaccurate, that is a bug in the page and will be treated as one.

Privacy and data

Questions about what this site does with your data are answered on the privacy page, which is deliberately specific rather than legalistic.

If something there is unclear, incomplete, or appears to contradict what the site actually does, that is worth an email. A privacy page that is wrong is a serious problem, not a wording quibble.

Please do not send tool input

One request. Do not paste tokens, private keys, credentials, certificates or production data into an email to demonstrate a problem.

The tools run entirely inside your browser precisely so that material never has to travel anywhere. Emailing it here would undo that protection for the sake of a bug report, and a description of the input is nearly always enough. If the exact bytes really are needed, a redacted or synthetic sample that reproduces the same failure works just as well.