Overview
Source list and handling process for DEF CON news, forums, badge threads, and community logistics.
Primary Watchlist
Use the official and community surfaces together. The official feed catches announcements, the forum carries longer-running organizer and attendee threads, and Reddit often surfaces logistics questions, badge rumors, meetup notes, and travel friction before they become polished writeups.
- Track https://defcon.org/defconrss.xml for official DEF CON announcements and publication updates.
- Track https://forum.defcon.org/ for event planning, badge-life, training, village, and attendee-support threads.
- Track https://www.reddit.com/r/Defcon/ for community questions, badge sightings, logistics, and post-event links.
Editorial Handling
Do not turn a single community post into a claim. Use Reddit and forum posts as leads, then verify against official DEF CON pages, speaker materials, repositories, or archived media before publishing a factual statement.
- Capture the source URL, publication date, and whether the item is official, organizer-adjacent, or community-reported.
- Separate confirmed announcements from rumors, predictions, and attendee chatter.
- When badge projects are discussed, link the public repository or maker page whenever available.
What Belongs On FLLC
DEF CON coverage should translate event energy into defensive value: what defenders can log, test, harden, automate, or teach from the talks and badge projects.
- Turn talks into lab ideas, detection questions, and enterprise control checks.
- Treat badges and hardware projects as embedded-systems learning material.
- Keep offensive technique discussion bounded to authorization, lab scope, and defensive outcomes.