general + corrections
contact@fishhooklabs.com
Gear corrections, disputed rules, spec errors, guide requests, and anything else editorial. This is the one you want unless it is a legal matter.
Contact
Two addresses, no form
This site is entirely static and has no backend, so there is nothing here that could receive a form submission. Email is the whole contact surface, which also means your message is not passing through a third-party form processor.
rights + takedown
takedown@fishhooklabs.com
Copyright, trademark, image rights, and other legal notices. Include the exact URL, the material at issue, and the basis of your claim so it can be actioned without a round trip.
Corrections are wanted, not tolerated
The compatibility engine is only as good as the numbers behind it, and those numbers come from published specs that get misprinted, revised, and quietly changed between product runs. If something is wrong, telling us fixes it for every build on the site at once. There is no reputational cost to us in being corrected and a real cost in being wrong, so send it.
A gear correction
Include whatever of this you have. Even a partial report is useful.
- The part, as precisely as you can name it — brand, model, size or test.
- The field that is wrong: bore, diameter, rated strength, wire gauge, price band.
- The value we show and the value you believe is correct.
- Where your number comes from: the packaging, the manufacturer's spec page, or your own measurement. Say which, and say how it was measured if it was measured.
A disputed diagnostic
If the engine flagged a build you know is sound, or missed something it should have caught:
- The share link for the build. The studio keeps the entire build state in the URL, so copying the address bar sends us the exact configuration you are looking at.
- The diagnostic message, and the rule id printed under it if one is shown.
- Why you think it is wrong. "This is standard practice for X" is a legitimate argument and will be treated as one.
Rules get changed, the threshold gets moved, or we write back explaining why we are keeping it. All three are real outcomes.
Other reasons to write
- A component category or species we have not covered that you would use.
- A knot or technique guide that should be surfaced at a stage where it is not.
- Accessibility problems. These get priority over feature work.
- Privacy questions — see the privacy policy first, it may already answer it.
Response time
This is a small operation, so expect a few days rather than a few hours. Everything is read. Corrections that come with a source get actioned fastest, because they can be verified without a conversation.