Home/Community

Community

There is no forum and no mailing list. Readers send corrections, measurements and topic proposals through one channel, and everything published gets a public note when it changes.

Propose a topic

A useful proposal has three parts: the question, the device or toolchain it applies to, and the measurement you would accept as an answer. “How fast is Vulkan on mid-range phones” is not a topic; “what is the GPU cost of a four-cascade shadow pass at 1080p on a 2024 mid-range device” is.

State the question in one sentence.
Name the hardware class and the API level.
Say what result would change your mind.

Proposals are collected in the editorial queue, a plain text file in the project repository. Nothing is promised; the queue is public so you can see what is already planned and what was rejected.

Send a correction

Corrections with a command and a log are acted on within a week. Include the article, the paragraph, what you measured, and on which device. If the correction changes a number in a table, we re-run the measurement before editing; if we cannot reproduce it, the article gets a note saying so rather than a quiet change.

Send a measurement

We publish reader measurements when they fill a gap we cannot test: a device class we do not own, a vendor driver we cannot install, a game genre we do not run. Send the method along with the numbers. A table without a method is an anecdote, and we will ask for the method before using it.

What we do not do

No guest posts, no sponsored content, no “collaborations” that are advertising.
No individual email addresses, no direct messages, no private support.
No names of readers without permission. A measurement can be published with the device class alone.

Code of conduct

Be specific and be kind. A correction is not an attack, and a disagreement about a benchmark is not a disagreement about a person. Submissions that contain someone's private information, or that are written to waste an editor's time, are discarded without a reply.