Reported
David Hogg's Data Center Tweet Draws Mockery After Community Note
News record
David Hogg wrote that if data centers are essential and beneficial, they should prove it by being built in the richest U.S. ZIP codes first.
Evidence state
developing
Any correction or response from David Hogg, the Community Note's source pages in accessible retained form, and registered-outlet reporting that distinguishes the post from reactions.
Reported vs. the record
The record
Hogg's canonical post retains his richest-ZIP-code data-center proposal.
Primary-source receiptReceipts
- captured headline
David Hogg's Data Center Tweet Draws Mockery After Community Note
- screenshot timestamp
screenshot timestamp
- subject identity
subject identity
The canonical @davidhogg111 post directly identifies Hogg as the publisher of the retained data-center statement.
Open source receipt - originating speaker
Hogg directly proposed that data centers should prove their benefits by being built in the richest U.S. ZIP codes first.
Direct fetch retained the canonical account, exact wording, replied-to post, Community Note, and timestamp.
Open source receipt - reporter publication
Hogg's X account published the underlying statement and now displays the Community Note and replies.
The canonical post was directly fetched and visibly contains all three components.
Open source receipt - atomic claim
David Hogg wrote that if data centers are essential and beneficial, they should prove it by being built in the richest U.S. ZIP codes first.
The claim follows the directly fetched wording and treats the statement as an attributed proposal, not a factual assertion about existing locations.
Open source receipt - primary source evidence
Hogg's canonical post retains his richest-ZIP-code data-center proposal.
The canonical post was directly fetched and its retained URL-plus-statement payload was content-hashed.
Open source receipt - primary source evidence
The same canonical post visibly retains the Community Note about Loudoun County's income and data-center concentration and links its sources.
The displayed note was directly fetched and its retained URL-plus-note payload was separately content-hashed.
Open source receipt - response correction
The fetched thread displays multiple insulting or mocking replies; these are opinion reactions and provide no additional resolution evidence.
Direct fetch shows named replies and wording, while the receipt explicitly separates rhetoric from the factual Community Note.
Open source receipt - resolution evidence status
Hogg's proposal, the attached Community Note, and mocking replies are retained, but no Hogg correction or response and no registered cross-publication coverage were found.
The direct record establishes the exchange while leaving the policy argument and any later response open.
Open source receipt
This page is a source-linked record. It does not score a person, infer motive, or replace the preserved source material.