[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-appeals-court-limits-doj-bid-for-journalists-linkedin-messages":10,"sections":41},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":22,"persona_id":22,"persona_name":22,"section":30,"tags":31,"sources":36,"feedback":40,"feedback_at":22,"cost_usd":40,"total_tokens":40},12890,"appeals-court-limits-doj-bid-for-journalists-linkedin-messages","Appeals Court Limits DOJ Bid for Journalists' LinkedIn Messages","An appeals court said the DOJ cannot sweep in journalists with no link to a leak probe, and faulted a year-long secrecy order that kept them in the dark.","An appeals court has told the Justice Department it cannot use a leak investigation to collect LinkedIn data on journalists who have \"no conceivable relationship\" to the case.\n\nThe DOJ was looking into suspected leaks of top-secret military information tied to a news report that President Trump said exposed confidential military information in a foreign country. It asked LinkedIn for 18 months of communications from targeted journalists, who together published more than 1,000 articles on many different topics in that period. The request was not limited to the reporters behind the story. It also reached journalists with any possible link to them around the time the report was drafted.\n\nLinkedIn argued that most journalists keep accounts on the platform and publish their contact details to invite sources to reach out. The judges agreed the harm went beyond the targeted reporters, ruling that the request threatened a platform where journalists routinely connect with confidential sources. They also pointed to \"a vast number of confidential sources\" caught up in the demand.\n\nThe secrecy order may be the more unusual detail. The administration secured an order barring LinkedIn from telling anyone about the request for a year. The judges ruled that this left journalists unaware for far too long that their First Amendment rights had been compromised.\n\nThe scope problem is easy to see. A reporter's notebook sits in a desk drawer; a reporter's LinkedIn inbox sits on a company's servers, and the \"contact me\" invitation that makes the platform useful also makes it a ready-made list of sources. Government pursuit of reporters' records is not new. In 2013, the Justice Department drew heavy criticism for obtaining Associated Press phone records. What differs here is the breadth of the net and a platform that holds years of messages.\n\nThe open question is the gag. When the company holding the data is barred from speaking for a year, who is positioned to object on behalf of the people whose messages are at stake?","[\"linkedin\",\"press-freedom\",\"doj\",\"privacy\"]","2026-11-11T18:05:26.000Z","2026-11-11T20:37:51.275Z","2026-11-11T20:37:51.661Z","published",null,[24],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"The source says only that the ruling came 'Tuesday', so 'November 10' is an unsourced date (it falls on a Monday in 2025); verify the date or use the source's wording. Also cut or source the claims about what the ruling does and doesn't say ('does not say leaks cannot be investigated', 'LinkedIn was the only party that knew'), and name the court if it can be verified.","resolved","policy",[32,33,34,35],"linkedin","press-freedom","doj","privacy",[37],{"name":38,"url":39},"Ars Technica","https:\u002F\u002Farstechnica.com\u002Ftech-policy\u002F2026\u002F11\u002Ftrump-admin-loses-fight-to-spy-on-random-journalists-linkedin-dms\u002F",0,{"sections":42},[43,48,53,58,62,67,72,77,82,87,92,97,102,107],{"name":44,"slug":45,"count":46,"latest_published_at":47},"AI","ai",7144,"2026-11-12T13:27:45.000Z",{"name":49,"slug":50,"count":51,"latest_published_at":52},"Security","security",1128,"2026-11-11T18:05:00.000Z",{"name":54,"slug":55,"count":56,"latest_published_at":57},"Deals","deals",642,"2026-11-12T14:00:00.000Z",{"name":59,"slug":30,"count":60,"latest_published_at":61},"Policy",619,"2026-11-12T12:53:36.000Z",{"name":63,"slug":64,"count":65,"latest_published_at":66},"Consumer Tech","consumer-tech",364,"2026-11-12T11:12:32.000Z",{"name":68,"slug":69,"count":70,"latest_published_at":71},"Hardware","hardware",336,"2026-11-12T11:24:43.000Z",{"name":73,"slug":74,"count":75,"latest_published_at":76},"Science","science",230,"2026-11-12T10:00:00.000Z",{"name":78,"slug":79,"count":80,"latest_published_at":81},"Software","software",168,"2026-11-11T17:36:49.000Z",{"name":83,"slug":84,"count":85,"latest_published_at":86},"Startups","startups",159,"2026-11-11T12:30:00.000Z",{"name":88,"slug":89,"count":90,"latest_published_at":91},"Dev Tools","dev-tools",127,"2026-11-11T19:00:44.000Z",{"name":93,"slug":94,"count":95,"latest_published_at":96},"General","general",118,"2026-11-11T16:49:42.000Z",{"name":98,"slug":99,"count":100,"latest_published_at":101},"Gaming","gaming",107,"2026-11-12T10:09:03.000Z",{"name":103,"slug":104,"count":105,"latest_published_at":106},"Reviews","reviews",38,"2026-10-20T12:00:00.000Z",{"name":108,"slug":109,"count":110,"latest_published_at":111},"How-To","how-to",8,"2026-10-05T09:00:00.000Z"]