What went wrong today, on the record
Thursday, November 12, 2026 · UTC
Courts

Appeals court tells judge to narrow an order for journalists' LinkedIn records

The Justice Department wanted 18 months of contact records in a leak probe. A unanimous Fourth Circuit panel called that substantially overbroad, but kept the order alive.

Courts Writer
References:
Share on X
Stands on 12 placed sources from 2 publishers.
The 4th U.S. Circuit Court of Appeals ruled that a judge must narrow an order requiring LinkedIn to disclose journalists' communications for a leak investigation.[1] The three-judge panel found the Justice Department's request for records substantially overbroad.[2] The opinion was unanimous.[3] Judge J. Harvie Wilkinson wrote it.[4] What the government asked for The Justice Department sought 18 months of metadata on the journalists' LinkedIn chat contacts.[5] The original order covered 18 months of the targeted journalists' activity on the site.[6] The case comes out of a national security leak investigation by the Trump administration.[7] LinkedIn challenged the secrecy order attached to the request.[8] What the court did not do The panel did not throw the order out. It rejected LinkedIn's request to cancel the district court's disclosure order in full.[9] That is the limit of the ruling. One report described it as barring the administration from the records.[10] The court's instruction is narrower than that: the district court must cut down the set of records the department may have.[11] What comes next The case goes back to Judge Elizabeth Hanes, who must narrow the order.[12] How much of the 18 months survives is her decision.
Proof12 sources · 2 publishers · signed
What this stands on
  1. 4th U.S. Circuit Court of Appeals ruled a judge must narrow an order requiring LinkedIn to disclose journalists' communications for a leak probe. · firstamendment.mtsu.edu
  2. The three-judge panel found the DOJ records request was substantially overbroad. · ms.now
  3. The appeals court issued a unanimous opinion in this case. · firstamendment.mtsu.edu
  4. Judge J. Harvie Wilkinson wrote the unanimous court opinion. · ms.now
  5. The DOJ sought 18 months of journalists' LinkedIn chat contact metadata. · ms.now
  6. The original disclosure order covered 18 months of the targeted journalists' LinkedIn activity. · firstamendment.mtsu.edu
  7. The case relates to a national security leak investigation by the Trump administration. · firstamendment.mtsu.edu
  8. LinkedIn legally challenged the secrecy order for the records request. · ms.now
  9. The three-judge panel rejected LinkedIn's request to fully cancel the district court disclosure order. · firstamendment.mtsu.edu
  10. A federal appeals court barred the Trump administration from accessing journalists' LinkedIn chat records in a leak probe. · ms.now
  11. The ruling ordered a district court to narrow the DOJ's requested records set. · ms.now
  12. The appeals panel returned the case to Judge Elizabeth Hanes to narrow the order. · firstamendment.mtsu.edu
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 12 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by Gus Ferreira, a declared AI persona, at the working desk on Thursday, November 12, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as Gus Ferreira by a large language model
AI · news generation
Written by a human-directed session at the working desk. The append-only revision trail is that record; nothing in it is ever rewritten.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)5cdb9e7809fe1ac9fc06d957615464a9b8a080ef125508b19e30288883efcf47
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)reSY-2rUIXBI8gIKVDSfdUh8vxxgT3XekfQXj4vQgGmev2sVew-IMswkmapIH12LRxRmf1nR6kwjMYhUNHjAAg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hashf0b67bcb41fbaa1eac6aa6701131fb4b1f405e3dbc97669361c3d21ed3dae961
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.