Contact · Corrections · Commissions

Every mailbox, and a form that needs no server

We answer technical mail. Include the versions, the exact command, signal or traffic you used, and what you expected to see instead. Corrections to published guides get priority, and every address below reaches a person rather than a ticket queue.

errata@ net@ audio@ gfx@ · hello@ corrections first routing & radio captures & chains how to write to us 1 · versions 2 · exact command or signal 3 · expected vs observed 4 · a file if you can what happens next read by a person answer, or an entry in errata corrected in public no trackers · no newsletter
5Mailboxes, all answered
0Trackers & analytics
0Data stored by this page
PublicErrata reviewed in the open

The form

Bring us a bug report, a measurement or a build photo

The form composes a message in your own mail client unless a delivery endpoint is configured, which means nothing typed here passes through a server we run. The addresses beside it always work, and they are the same mailboxes.

Send a message

Commands, measurements and error output welcome. Plain text is fine.

Nothing on this page is stored or tracked, and there is no newsletter to be added to. The addresses beside the form always reach us.

Or write to the right desk

  • Corrections & errata errata@polymathes.cc Reviewed in public
  • Networking net@polymathes.cc Weekly on the mailing list
  • Audio audio@polymathes.cc Weekly on the mailing list
  • Graphics & photography gfx@polymathes.cc Weekly on the mailing list
  • Press & licensing hello@polymathes.cc Within a few days

Routing

Which address to use

Sending directly to a desk skips a forwarding step and usually halves the reply time. If you are unsure, use the form or hello@polymathes.cc and we will route it.

Mailboxes, what belongs in them, and when you should expect an answer.
DeskAddressBest forTypical reply
Corrections & errataerrata@polymathes.ccSomething we published that is wrong, out of date or unsafe, with the measurement or citation that shows it.Reviewed in public, usually within a week
Networkingnet@polymathes.ccRouting, switching, firmware, radio links, audio over IP, network measurements.Weekly round, on the mailing list
Audioaudio@polymathes.ccNAM captures, TONE3000, signal chains, impulse responses, Linux audio plumbing.Weekly round, on the mailing list
Graphics & photographygfx@polymathes.ccRendering, colour pipelines, raw workflows, calibration, file formats and metadata.Weekly round, on the mailing list
Press & licensinghello@polymathes.ccCommissions, reuse of our documentation, speaking, press questions and anything legal.Within a few days

Practice

What happens to a message

Read

A person reads it, not a queue

There is no ticketing system, no autoresponder and no chatbot. Technical mail is read by the person who wrote the guide you are writing about, which is why versions and exact commands get a faster answer than a description of a feeling.

Published

Corrections are public

If your correction changes a page, the page is edited and the correction is credited there. We quote correspondence only with permission, and never publish an address, a file or a client detail without asking first.

Stored

Nothing is collected here

This site sets no cookies, loads no analytics and no third-party fonts, and the form does not touch a database. Mail lives in the mailbox it was sent to; ask and we will delete the thread.

Sensitive material. We do not publish a PGP key, because we would rather agree on a channel than pretend a key that never gets rotated is security. If you need to send something confidential — a client network diagram, an unpublished capture, a vulnerability — say so in a first message with no attachments and we will arrange the rest.

Elsewhere on this site

Before you write, it may already be answered

Licensing, governance and the way we work are documented in the open. The guides themselves carry their own provenance notes and errata.