Conference Coverage Methodology

If you read a conference report or talk summary on QuahogCon, it went through a few filters first. We don’t just show up and live-tweet everything. We pick events that matter to the community, attend with clear editorial goals, and write what we actually saw and heard. Here is how that works.

How we pick conferences

We look at three things: relevance to practitioner work, originality of content, and accessibility to the broader hacker community. A closed-door corporate summit with NDAs? Not our beat. A small, single-track village at a big con where someone is demoing a new exfiltration technique on real hardware? That is exactly what we want.

We also consider geographic spread and cost to attend. We skip cons that require a “press credential” that locks you out of workshops because we think hands-on access matters more than a press badge. We attend paid events when the content justifies the ticket, and we say so in our coverage.

On the ground

Once we are at a conference, we split time between talks, hallways, and hands-on areas. Talks get prioritized by novelty and practical impact. We skip the vendor keynote talks that are just product pitches. Instead, we sit in on the 8 a.m. talk about bypassing EDR with a custom driver, or the impromptu lockpicking competition running on a folding table.

We take notes by hand or on a local machine. No cloud transcription tools, no AI summaries. The write-up comes from what we actually heard, plus follow-up conversations with speakers afterward. If a demo broke mid-presentation or a slide had a typo, we mention it. That is the kind of detail you deserve to know.

Editorial independence

We do not take sponsored coverage. If a conference gives us a free ticket, we still report critically. If we paid our own way, we say that too. You will always see a disclosure line at the bottom of each article listing whether we received any compensation or access.

We also do not publish talk abstracts in advance. Pre written summaries from organizers often sand off the rough edges. Our coverage comes from direct observation. If a talk was cancelled or the speaker fumbled a live demo, that is part of the story. We trust you to judge the signal from the noise.

What you get

Expect a mix of long-form reports that walk through a conference day by day, and shorter tool reviews or technique guides that emerged from a specific talk. We also cross reference claims: if someone says their tool bypasses a specific defense, we test that claim ourselves or note when we couldn’t verify it.

Conferences are where the community shares raw, unfiltered knowledge. Our job is to capture that without polishing it into press release language. If you come to QuahogCon for conference coverage, you are getting the version you would hear if you were sitting next to us at the bar after a talk.