TorentsFewer steps, better Mac apps

Get in touch

Most questions have a home. Reaching the right inbox helps me reply quickly, so I have organized the contact paths by what you need. Read the short direction below, then send me a clear message.

Before you write

  • Licence keys, cracks, account recovery. I catalogue apps—I don’t build or sell them. For a lost licence key, an expired subscription, or a forgotten password, contact the developer directly. I cannot help with cracks either.
  • Program how‑to. Questions about using a feature or troubleshooting an app are better asked in the comments under that program. Someone who uses it daily often answers faster than I can, and the conversation stays visible for others.
  • Copyright concerns. If you hold rights and believe a listing should change, use the DMCA page. That is the only track reviewed by my copyright team.

Corrections to a page

A wrong version number, a typo, or a compatibility note that is out of date can throw off a whole workflow. I keep older builds listed for older Macs, so version‑label mistakes matter a lot. Send the program name, the detail that is off, and a link to the correct information when you can. I verify every correction against the developer’s own release notes before updating the catalogue.

Broken downloads or wrong links

If a download returns an error or a link points to the wrong domain, tell me the program name and the exact link that does not work. I test every report myself and update the listing if the official link has moved. When a developer retires an app, I note that on the page instead of leaving a dead link. Reports that include the build number help me spot version‑specific hosting changes faster.

Suggesting a program

I choose apps that remove busywork for small teams. Before you suggest one, check that it fits the catalogue: few steps, a clear outcome, and no feature sprawl. Describe what the tool replaces and why it saves time over the alternatives you have tried. I test every suggestion on my own Mac, but I do not publish a public roadmap of what I might add. A short, concrete note works better than a long pitch.

Write to me

For any of the above, email [email protected]. There is no form—just a plain message from your regular email client. I read every note that lands in this inbox. If a reply takes a few days, I am likely testing an app or updating compatibility notes for a new macOS release.