Contact TrenTyx – Bug Reports, Tool Requests and Press
One person reads this inbox, so a clear message gets a faster answer than a long one. Bug reports are especially welcome: these pages carry no error tracking, which means nothing tells the maintainer that a tool broke unless you do.
What to Send
Reporting a Wrong Result
A tool producing incorrect output is the highest priority category, and four details make it fixable in one pass instead of five:
- Which tool and, if relevant, which settings were active — dialect, mode, or comparison options.
- The exact input, or a reduced version that still misbehaves. A three-line example beats a three-hundred-line one.
- What you expected and what appeared instead. This matters more than it sounds, because some disagreements are about convention rather than correctness.
- Browser and version. Occasionally a bug is specific to one engine's handling of clipboard access, file downloads or number formatting.
Please strip anything sensitive before sending. If a query only fails with real production values, describe the shape of the data rather than pasting it — column types and structure are usually enough to reproduce a formatting or parsing bug.
Requesting a New Tool
Two conditions decide whether a request can be built. First, the work must be possible entirely in the browser; anything requiring a server-side key, a database, or a paid API does not fit the model this site is built on. Second, it should be a recurring chore rather than a one-off, because a tool nobody returns to is just maintenance debt. Saying how often you hit the problem helps more than describing the ideal interface.
Accessibility Problems
If something is unusable with a screen reader, a keyboard alone, or at high zoom, that is treated as a bug and not a feature request. Mentioning your assistive technology and its version speeds up the fix considerably.
Press, Listings and Partnerships
Questions about the project for an article, newsletter or directory listing are welcome, and factual details such as launch date, tool count and technology choices can be confirmed quickly.
Two things that will not receive a reply, stated plainly to save everyone time: paid guest post offers and link exchange requests. Neither fits how this site is built or how it earns its rankings.
Response Time
This is a personal project maintained alongside other work, so expect a reply within a few days rather than within hours. Messages that include enough detail to reproduce a problem are usually answered first, simply because they can be acted on immediately.
Security Reports
The tools process everything locally and store nothing, which removes most of the usual attack surface: there are no accounts, no sessions, no databases and no uploads. The realistic risk is a cross-site scripting flaw in how a page renders your input back to you. If you find one, please report it privately to the address above rather than publishing it, and include the input that triggers it. A fix and a public note will follow.