Get in touch
toolpack.dev is maintained by one developer, so messages come straight to me. Email is the only channel — there is no form here, because a form would mean sending your message through a server, and the whole point of this site is not doing that unnecessarily.
What is most useful to send
A bug in a tool. The most valuable report includes the tool, the exact input, what you got, and what you expected. Input matters more than anything else — most tool bugs only appear with a specific value, and a description without the input is usually not reproducible.
A correction to an explanation. The technical write-ups under each tool are meant to be accurate, and getting them right is the point of writing them. If something is wrong, oversimplified, or out of date, tell me — this is the most welcome kind of message.
A tool request. Say what problem you are trying to solve rather than just naming the tool. Knowing the actual task often changes what gets built.
Advertising or sponsorship. Reasonable, non-intrusive placements are possible. Anything that pops up, follows the scroll, or sits above a tool is not.
What I cannot help with
I cannot debug your application, review your code, or recover data. And I cannot see anything you pasted into a tool — that data never reaches me, so if you want me to look at a case, you will need to include the input in your message.
Response time
This is a side project, so replies take days rather than hours. Bug reports with reproducible input get answered first.
Security issues
If you have found a security problem with the site itself — an XSS vector, a way to make a client-side tool leak data, anything in that category — please email it rather than posting it publicly, and I will fix it and credit you if you would like.