Tech

The newsroom coffee tastes like burnt subpoenas. Sirens outside, committee mics inside. Washington is doing its favorite trick again: calling it “national security” while asking you not to read the fine print. The new deadline drama is FISA Section 702, with Congress barreling toward reauthorization and reformers begging lawmakers to stop a second, quieter surveillance pipeline: the government buying your private data from brokers like it is office supplies.

What Congress is fighting about: Section 702, “backdoor searches,” and the data broker loophole

Section 702 is sold as foreign surveillance: collection of foreign communications overseas without a warrant. That is the brochure. The fine print is that once the system hoovers up huge volumes of communications, agencies can search within it in ways that touch Americans too, including what privacy advocates call “backdoor searches.”

NPR reports that a 2022 Foreign Intelligence Surveillance Court document described FBI violations as “persistent and widespread,” and that transparency reporting has documented searches involving a U.S. senator, journalists, and campaign donors, among others.

Now the program is up against an April 20 deadline. Axios reports the White House is pressing for a “clean” extension and leaning on Speaker Mike Johnson to move it, including hosting skeptical lawmakers ahead of the expected vote.

Meanwhile, 53 members of Congress led by the chairs of CAPAC, CHC, and the Congressional Progressive Caucus sent a letter demanding Fourth Amendment guardrails. They called out the “data broker loophole,” saying agencies including the FBI, DHS, the Department of Defense, and the IRS are already purchasing Fourth Amendment-protected data from commercial data brokers without warrants or court orders.

Translation: “Clean extension” means “keep the factory running”

Translation: in Washington, “clean” often means “untouched.” No amendments. No safety inspections. No friction for the surveillance machine.

And the “data broker loophole” is the oldest hustle in the compliance handbook. If a warrant is inconvenient, you outsource the extraction to private companies and buy the results. That is not a magical constitutional workaround. That is laundering with a purchase order.

Here is the mechanism: surveillance by procurement, accountability by shrug

Here is the mechanism: the invasive step is not a judge signing a warrant. It is a procurement officer approving a contract. Data gets collected, bundled, and resold, and the government sidesteps the courtroom by walking through the contracting office.

NPR notes FBI searches for Americans in Section 702 data have declined dramatically in recent years based on bureau disclosures, while also pointing to oversight gaps, including a Justice Department watchdog report describing a now-shuttered tool that allowed untracked searches.

Follow the money: brokers get paid, agencies get deniability, you get watched

Follow the money: data brokers profit by turning your life into a commodity. Then agencies use taxpayer dollars to buy it, turning a predatory market into a public subsidy for surveillance capitalism. Private firms get revenue. Agencies get deniability. Politicians get to thump a lectern and call it leadership.

The quiet part is simple: if they can buy it, they do not have to justify it. If they do not have to justify it, they do not have to stop. And whatever gets renewed now outlives the next election.

Mic-drop: if Congress cannot close the data broker loophole while reauthorizing Section 702, they are not balancing security and liberty. They are choosing the side that surveils. The accountability tools are boring on purpose: audits of agency purchases, inspector general pressure, court challenges, public records fights, and organizing that treats privacy like a civil rights and labor issue, not a boutique hobby.

I spent part of last night in the usual American cathedral: the laptop glow, the dusty civics habit, and that faint scent of bureaucratic paper cuts. Somewhere, someone was probably saying “national security” like a magic word and hoping nobody checks the trap door.

But the trap door is not theoretical. It is patched, unpatched, and exploited in the wild.

CISA updated the “patch this now” list

On April 13, the Cybersecurity and Infrastructure Security Agency (CISA) updated its Known Exploited Vulnerabilities (KEV) catalog, the government’s running ledger of flaws attackers are actually using. Multiple reports describe the update as a batch of six vulnerabilities across Microsoft, Adobe, and Fortinet, with a remediation deadline of April 27 for federal civilian agencies.

Two details matter for anyone who likes their systems stable and their liberties intact:

• Some of this is old. One vulnerability cited in coverage dates back to 2012.
• Some of this is everyday infrastructure. Coverage points to issues tied to Windows and Exchange Server, plus Adobe Acrobat/Reader, and Fortinet software used to manage endpoints.

There is also a small but telling disagreement in public reporting about the count: some outlets describe a seventh CVE (an Adobe Acrobat/Reader issue) in addition to the six listed elsewhere. Inside baseball, sure. But it is also a snapshot of the broader problem: the vulnerability ecosystem is noisy, and patch discipline is uneven enough that even counting the fires can become an argument.

The tradeoff: fewer breaches now, or more surveillance later

When basic cyber hygiene fails, the political sequel is predictable: emergency purchases, expanded monitoring, broader logging, more data sharing, and “temporary” authorities that stick around like glitter after a parade.

Patching is boring. It is also the cheapest civil-liberties policy you can buy, because the pressure after a breach rarely lands on the neglected patch queue first. It lands on the public’s privacy, with new proposals to scan more, retain more, and watch more “for safety.”

The Orwell check

Watch the language. “Visibility” can mean sensible asset inventory. It can also mean permanent inspection. “Threat hunting” can be narrow, measured, and audited. It can also become a polite euphemism for fishing expeditions once the tools exist and the fear is fresh.

The liberty ledger (and one nuance)

Who pays when exploited vulnerabilities linger? Regular people: their medical records, tax data, credentials, small businesses, and privacy. Who wins? Attackers, and the folks who treat security like a quarterly mood.

One nuance: CISA’s KEV process is a prioritization tool, not a crystal ball. CISA has emphasized that adding a vulnerability to KEV does not always mean it is seeing active exploitation at that exact moment.

The Paine test and the guardrails

Do we want a future where preventable cyber failures concentrate more power in centralized monitoring, or one where institutions do the basics well enough that they stop asking for new powers every time the roof leaks?

Guardrails that help without building a digital panopticon:

• Mandatory, public, plain-English patch performance reporting against KEV items.
• Procurement muscle: demand secure defaults, long support windows, and rapid fixes, or stop buying repeat offenders.
• Defensive monitoring tied to due process: scoped, audited, access-controlled, and retention-limited. No forever logs “just in case.”

Liberty loves boring. What would it take for your organization, or your government, to treat patching exploited vulnerabilities as a civil-liberties obligation instead of an IT chore?

Picture hickory smoke meeting printer toner, and then the courtroom starts sounding like a radio that got hit with static. In New Mexico, judges are not letting AI-generated legal filings slide when they come back with fake citations, fake facts, and pure hallucination fuel.

AI errors pop up in New Mexico filings

Reporting on April 13 says federal and state courts in New Mexico are increasingly spotting false or misleading filings tied to generative AI tools. This is not a tech apocalypse. It is a proof-of-work problem for grownups: when the paper claims something is true, somebody has to verify it, or the judge has to step in as quality control with real sanctions.

When the AI lies, the judge grabs the tongs

One example in the reporting involves a pro se federal lawsuit where a damages request was described as quite simply ludicrous by Senior U.S. District Judge Judith Herrera. The case did not end in a mic drop. It ended with sanctions noted at $8,640 after the court found issues in filings tied to AI hallucinations.

Here is how the junk spreads: generative AI can produce citations that look official. If someone copies and pastes that output, the courtroom becomes the place where the system gets tested in public. It is like ordering brisket and getting a plate mostly made of smoke and mirror charts.

Courts have also described warnings and sanctions in multiple matters since 2023, including situations where citations in a filed brief were made up. In a separate example discussed by a legal blog, a judge ordered a $1,500 fine and additional steps after finding cited cases did not exist, including a requirement aimed at legal ethics and AI use.

Disclosure beats denial

Judges are also demanding transparency. One New Mexico judge, John P. Sugg, reportedly imposed an order requiring anyone who uses generative AI to draft, edit, or modify court papers to disclose that use at the top of the filing. The order also requires certification that the AI-produced language was checked for accuracy using traditional methods or by a human being.

Who benefits, and what this means for freedom

The villain is the grift ecosystem that sells speed and confidence while offloading verification onto people who do not want to do the hard work. The incentive is money and power. If you file faster, charge faster, and dodge responsibility, you keep the cash rolling and avoid the embarrassment of admitting you never checked the citations.

Meanwhile, the judge benefits because the courtroom stops wasting time on phantom authorities. The opposing party benefits because they are not forced to fight ghosts. And Americans benefit because legal outcomes and public records cannot be built on fabricated sources.

So yes, it is a tech story. But it is also a constitutional story about process. If you are going to speak in court, you disclose your method and verify your claims. Otherwise, you are just hauling paperwork full of smoke.

Tell me straight, folks: are you more worried about AI getting regulated, or about people getting away with filing made-up facts in the name of speed and free speech?

The newsroom fluorescents hum like a cheap lie detector. My coffee tastes like burnt toner. On my screen, the same sanitizing phrase keeps popping up, laundered by lawyers and national security theater: a “clean” extension.

Clean. Like a scalpel that never has to answer questions.

Bloomberg Government reported April 13 that H.R. 8035 would extend FISA Title VII, including Section 702, without changes, moving the expiration to October 20, 2027. It is pitched as an 18-month extension, the kind of calendar math Washington uses when it wants you focused on the deadline, not the power.

That deadline is real: Section 702 expires April 20, 2026, and the House is expected to vote this week on reauthorization. Cue the panic confetti. Fentanyl. Terrorists. Foreign spies. The familiar chant of “do not read the fine print.”

Meanwhile, the fine print is you.

What Section 702 is, and why Americans are still in the blast radius

Section 702 is aimed at foreigners located outside the United States. But it also sweeps up Americans’ communications incidentally. Later, agencies can search that collected pool for Americans’ communications using so-called “U.S. person queries,” without a traditional warrant. The Brennan Center lays out the structure plainly, including how companies become the compliance pipeline: firms like Google and telecom giants are directed to hand over communications tied to foreign targets.

WSHU reported April 13 that supporters argue the tool is used every day, and they cite reforms passed in 2024. Opponents call it a privacy invasion. The split is not neatly partisan because surveillance is one of the few bipartisan hobbies that never goes out of style.

Translation: “Clean extension” means “no new handcuffs for the people doing the spying”

Translation: “Clean” means unchanged. No new friction. No new judge. No new consequences. No new warrant requirement for searching Americans inside the 702 pile. Clean for the operators. Not for the people being searched.

Your communications are not just content. They are context, association, the social graph. The union hall call list. The protest carpool thread. The journalist-source relationship that becomes “incidental” right up until it becomes “relevant.”

Here is the mechanism: the dragnet meets the search bar

Here is the mechanism: 702 collection creates a large reservoir of data under court-approved procedures, without individualized court approval for each target. Then agencies run searches inside that reservoir. Call them “U.S. person queries.” Call them “backdoor searches.” Same motion: you are in the pool, and they decide later whether to look for you.

Follow the money: infrastructure, compliance, and political convenience

Follow the money: Big Tech and telecoms are not bystanders. They are infrastructure. They may be ordered to provide data, but compliance becomes a system, a set of rails, an operational reality that can be treated like any other workflow.

And the political class gets the easiest bargain in Washington: sell fear, trade oversight for access, then call warrants “unworkable” when what they mean is “inconvenient.”

On April 10, Senator Ron Wyden said the Foreign Intelligence Surveillance Court found major compliance problems related to Section 702, and warned the administration was considering appealing the court ruling rather than fixing the underlying compliance mess.

The quiet part: the push for “clean” is about keeping the search capability effortless.

Section 702 expires April 20, 2026 unless Congress renews it. If lawmakers can authorize sweeping power, they can justify it in daylight. Hearings. Declassification of the court finding Wyden referenced. Inspector general audits with teeth. Court challenges that treat the Fourth Amendment like a rule, not a suggestion.

The newsroom coffee tastes like burnt compliance. Outside, sirens bounce off glass towers where the privacy policy is always a bedtime story and never a contract. On my screen: PDFs, press releases, and the same old loop. Take the data. Deny the data. Settle the case. Keep the leverage.

This one is not subtle. The Federal Trade Commission says OkCupid shared users’ personal information with an unrelated third party in September 2014, despite privacy promises that said otherwise. The alleged package was ugly: nearly three million user photos, plus location and other information. The FTC identifies the third party as Clarifai, known for AI tooling including facial recognition. The agency says users were not told, and were not given a chance to opt out.

Then came the long tail. The FTC alleges Match and OkCupid took extensive steps for years to conceal and deny the data sharing, including trying to obstruct the investigation. If that reads like a filing cabinet falling down a stairwell, good. It should.

What the FTC filed, and where it landed

On March 30, 2026, the FTC announced action against OkCupid and affiliate Match Group Americas, tied to OkCupid’s operator Humor Rainbow, Inc. The FTC filed a federal complaint and a proposed stipulated order in the U.S. District Court for the Northern District of Texas, Dallas Division.

The FTC alleges OkCupid gave an unauthorized third party access to millions of users’ personal data, including nearly three million photos plus location and other information, without formal or contractual restrictions on how the data could be used.

And the incentive story is right there in the complaint’s framing. The FTC says the third party sought the large datasets because OkCupid’s founders were financial investors in that third party.

Translation: “shared” means your face became inventory

Translation: when a company says it “shares” data, it turns your life into a transferable asset. A face becomes a row in a table. A location becomes a coordinate to be joined with other coordinates. Then somebody calls it “product improvement” so it sounds like nicer fonts instead of more surveillance capacity.

Dating data is intimate infrastructure. It’s not just “personal.” It’s where you are, how you describe yourself, and what you disclose when you think you are talking to a potential partner, not an AI training pipeline.

Here is the mechanism: promises as marketing, enforcement as paperwork

Here is the mechanism: platforms make privacy promises broad enough to soothe users and flexible enough to feed partners. The upside is immediate. The downside is theoretical. When the downside becomes real, time becomes the defense.

The proposed settlement’s core consequence, as described publicly, is a permanent prohibition on misrepresenting the extent to which they collect, use, disclose, delete, protect, or maintain personal information, including the purposes and user choices under state privacy laws. It’s not nothing. But it is not a time machine. You cannot unring a bell from 2014.

Follow the money: the fine is missing, the extraction is not

Follow the money: the FTC press release does not announce a monetary penalty. Media coverage points to a structural reality of U.S. privacy enforcement: often the agency cannot seek civil penalties for first-time violations under certain statutes without specific penalty authority.

The quiet part: enforcement without meaningful financial consequence becomes a rehearsal. Companies learn the choreography: deny, delay, settle, promise not to do it again, and keep the institutional knowledge of how to do it faster next time.

I keep thinking about the John Adams Courthouse in Boston: an old civic lung that smells like paper, polish, and arguments that outlive all of us. You can practically hear the Constitution clear its throat. The Massachusetts Supreme Judicial Court just reminded Meta of a basic rule from the town-hall textbook: a shield is not a cloaking device.

Section 230 is famous for protecting online services from being treated like the publisher of user-posted content. But it is not meant to be a magic cape that covers everything a company builds, markets, and promises.

What the court did (and did not) do

The Massachusetts Supreme Judicial Court ruled Meta has to face the Commonwealth’s lawsuit accusing the company of designing Instagram to induce compulsive use by children, and of misleading the public about safety and age protections. Meta wanted the claims tossed early under Section 230 of the Communications Decency Act.

At the motion-to-dismiss stage, the court did not buy that immunity argument as the claims were pleaded. The distinction is plain: the Commonwealth is not suing because teens posted something nasty. It is suing over Meta’s own alleged conduct, including product design and what Meta allegedly said about that design and its safeguards. The opinion was written by Justice Dalila Argaez Wendlandt.

One procedural note matters: this reached the court on an interlocutory posture. The justices concluded Meta could appeal at this stage based on the nature of the immunity claim, then concluded the immunity does not fit these claims as pleaded. That is not a final verdict on the facts, but it is a very loud door opening.

The Orwell check: the euphemism arrives before the power

“We’re just a platform” is the nicest euphemism Big Tech ever sold. If every design choice is relabeled “publishing,” then every harm becomes someone else’s content problem. Infinite scroll becomes free expression. Autoplay becomes the marketplace of ideas. Push notifications become a civic service. That is not reasoning so much as branding with footnotes.

The liberty ledger: kids, speech, and privacy

• Protect what Section 230 is for: shielding services from liability for other people’s speech, so the open internet is not strangled and only the richest speakers survive.
• Don’t confuse that with product accountability: claims rooted in a company’s own design choices and alleged misrepresentations are a different category.
• Watch the “protect kids” pivot: it often slides into age verification, then “upload your ID,” and suddenly we are building a permanent identity checkpoint for ordinary speech and browsing.

The tradeoff: accountability without an internet airport-security line

Courts can keep forcing clarity on what Section 230 covers and what it does not, and demand evidence before sweeping remedies. Legislators can aim narrowly at deceptive safety claims and manipulative design, and fund independent audits with real teeth. Regulators and attorneys general can police misrepresentation without smuggling in speech controls. And the public should insist on privacy guardrails any time age verification is pitched as the cure, because data collected for child protection has a habit of being reused for everything else.

One question for the comments section: if Section 230 is not a blanket defense for product design and alleged deception, will lawmakers write smart, privacy-safe rules, or reach for the nearest “show me your ID” button and call it safety?

That burnt-electronics smell is the kind of warning you cannot ignore. In this case, it came from Winona County’s networks after a ransomware attack, turning the daily digital neighborhood into something that sputters and stalls when you need it most.

Minnesota National Guard deployed to help Winona County

According to reporting on April 10, 2026, Gov. Tim Walz authorized the Minnesota National Guard to help Winona County respond after the county detected a ransomware attack on Tuesday. The county said affected systems were taken offline and residents should expect delays, while emergency services continued to operate. In other words: the plug got pulled to protect operations, but key services stayed up.

The county also described this as a separate incident from a January cyberattack. Officials said their preliminary investigation indicated it was not the same cybercriminal as the previous hit. That distinction matters because response work depends on knowing what threat actor you are dealing with, and what you might have to hunt for next.

Walz called the Guard, and the Guard brought expertise

Reporting described the Guard sending 15 experts from its cybersecurity team. The county’s emergency management director, Ben Klinger, said the experts helped local staff work faster and more deeply as the county hardened its network and added even more security. In additional accounts, Klinger and state and federal partners described taking the network offline out of caution, then restoring systems in phases while verifying each system’s security before bringing it back online.

Lt. Col. Brian Morgan, a Guard cyber coordination cell director, said these threat actors are typically financially motivated. The playbook described was straightforward: they try to gain access, ransom availability of the network, then, if they can, seek data and attempt extortion by threatening to release stolen information unless they get paid.

Why local governments are easy targets

University of Minnesota professor Jonathan Wrolstad explained that cities and counties often have fewer resources than larger organizations, yet still must keep day-to-day services running. That pressure can make them lucrative targets because ransomware crews know public-facing services cannot simply go dark.

What it means: cyber is part of national defense

When the Guard has to step into the IT gap, the lesson is hard to miss. Cybersecurity is not just an optional technical task. It is part of national defense because local systems support how the nation functions. Take down a county’s main network and you can get delays that regular Americans rely on. Take down emergency-adjacent systems and you risk slowing help when seconds matter.

Winona County took affected systems offline and worked to restore in phases, and the Guard provided expertise when it mattered. Now, officials and decision-makers should treat cybersecurity readiness as essential, with serious resourcing, faster threat intelligence sharing, accountability for underinvestment, and practical recovery playbooks that anticipate attacks rather than improvise after the fact.

The coffee tastes like scorched plastic and the newsroom scanner is doing that anxious stutter it reserves for stories that are both obvious and ignored. Somewhere, a water operator is staring at a screen that was never meant to be reachable from the open internet. Somewhere else, a vendor is emailing a PDF that says mitigation while the invoice says overtime. And in the middle, federal agencies have finally said the quiet part out loud: Iranian-affiliated hackers are actively targeting the machinery that keeps Americans alive.

Federal warning: water and energy control systems are in the crosshairs

On April 7, the EPA, FBI, CISA, and NSA issued a joint advisory warning US organizations, including the water sector, about an urgent and ongoing Iranian-affiliated cyber threat. The advisory says the activity has already caused disruptions and financial losses across multiple critical infrastructure sectors. It also highlights attacks against internet-facing operational technology, including programmable logic controllers that run industrial processes.

This is not a vibes memo. It is a federal flare. We are talking about the systems behind the systems: pumps, valves, controls, industrial control systems. When you corrupt the inputs, the outputs get physical.

Coverage quickly amplified the industrial-control angle and the named sectors: water and wastewater, energy, and government facilities. Some reporting points to broader cyber risk during the US-Israel war with Iran that began February 28, 2026, while noting that real-time attribution and incident linkage can be murky. Fine. The advisory itself is not murky about the core fact: attacks are happening, and they are hitting systems that should not have been this exposed.

Translation: someone is trying to grab the steering wheel

Translation: when the warning says Iranian-affiliated actors are exploiting internet-exposed PLCs and manipulating what operators see on HMI and SCADA displays, it means someone is trying to reach through the screen and move real equipment. Not just steal data. Move the levers. Change set points. Disrupt operations. Force shutdowns. Rack up losses. Shake public trust.

Translation: when agencies tell you to urgently harden systems, they are also admitting that too many systems are still running on bargain-basement security, with duct tape where perimeter design should be.

Here is the mechanism: privatize resilience, socialize the damage

Here is the mechanism: smaller water and wastewater utilities live on constrained budgets and layered mandates. They must deliver safe service 24/7 while keeping rates politically palatable. Meanwhile, the security market sells protection like a luxury good. Incentives push risk downward until it lands on the least resourced people operating the most consequential systems.

Federal guidance arrives as a document. The work arrives as labor: midnight patch windows, asset inventories that never existed, segmentation projects that should have been funded years ago, training, monitoring, incident response retainers, and hardware replacements. When an incident hits, the public pays twice: once for the federal response ecosystem, and again in local costs, disruptions, or higher rates.

Follow the money: the hack is the headline, the contracts are the plan

Follow the money: every warning like this is a market signal. Vendors hear cash registers. Consultants smell multi-year programs. Contractors pitch managed services. Insurers rewrite exclusions. And operators get squeezed between threat actors on one side and procurement bureaucracy on the other.

The quiet part: a lot of infrastructure runs on tech never designed for hostile networks, then gets connected anyway. And we are being prepped to accept water and power wobble as the new normal. That is a policy choice disguised as a weather report.

Yes, Iranian-affiliated actors should be confronted and contained. But if control devices are exposed, the adversary is not the only culprit. Demand receipts: audits, enforceable cybersecurity requirements tied to funding, regulators with staffing and teeth, sustained modernization money without predatory contracting, and security baselines that vendors meet by default, not as an upsell.

If the government can issue a joint advisory, it can build a joint accountability regime. Courts, watchdogs, inspectors general, procurement rules, labor organizing inside utilities and agencies, and elections that treat infrastructure like life support, not a talking point.

I keep an old civics textbook on a shelf that sags like it has carried too many promises. In the clean little diagrams, markets work because information is legible and the referee is awake. Then I open a modern checkout page and watch the price shape-shift like a witness who suddenly remembers details right after the lawyer says, “objection.”

FTC: StubHub must refund $10 million over mandatory fees

On April 9, the Federal Trade Commission filed a complaint and a stipulated order in federal court in Manhattan alleging StubHub violated Section 5 of the FTC Act and the FTC’s Rule on Unfair or Deceptive Fees. The agency says StubHub advertised ticket prices without clearly and conspicuously disclosing the total price, including mandatory fees.

The settlement requires StubHub to pay $10 million for consumer redress and includes injunctive terms intended to stop the pricing trick from reappearing.

The timeline (because power lives in the docket)

• The FTC’s Fees Rule took effect May 12, 2025.
• The FTC alleges StubHub failed to show the total price across its early pricing displays during a short window in mid-May 2025.
• The FTC highlights the run-up to the NFL schedule release on May 14, 2025.
• The FTC points to a May 14, 2025 warning letter and says StubHub fixed the issue the next day.
• The redress is meant for eligible consumers who bought U.S. live-event tickets between May 12 and May 14, 2025, through a distribution program, with a deadline in the order for providing that redress after the order date.

If your eyes glaze over at case paperwork, I get it. But in a world built to distract you, court filings are one of the few places left that still demand nouns, verbs, and consequences.

The Orwell check: when “fees” become a fog machine

The problem is not the poetry of the surcharge. It is the blunt fact that the advertised price was not the price. The FTC’s message is simple: if you show a price, show the total price up front and show it wherever you show a price. Otherwise, comparison shopping becomes a carnival game with better fonts.

The liberty ledger: who gains freedom, who gets squeezed

In drip pricing, consumers lose the freedom to make an informed choice at the moment it matters. Honest competitors lose the freedom to compete on the merits when the click goes to the lowest teaser number. The platform gains the freedom to monetize confusion.

Notice what is not happening: the government is not setting ticket prices or banning secondary markets. It is saying, do not misrepresent the total.

The tradeoff and the Paine test

Yes, compliance costs money and engineering time. But the tradeoff consumers have been forced into is worse: speed and convenience in exchange for surrendering clarity until the last screen. Run the Paine test: does enforcement expand liberty or concentrate it? On balance, it expands liberty by restoring the freedom to see the real price and say no before the final click.

Now the follow-up: who watches the watchers? The court should scrutinize the order. The FTC should be transparent about how redress is calculated and distributed. Watchdogs and auditors should treat the refund program like a public project, not a corporate apology tour. And Congress should write clear, durable statutes on all-in pricing and digital dark patterns.

Because if a major platform will play games with something as basic as the total price, what do you think it does with the harder stuff: your data, your attention, your ability to leave?

You ever hear a laptop fan wind up like a swamp cooler in August? That is the sound I picture when lawyers start filing in a tech fight. This time the legal grill belongs to Apple. The company wants the court to send a Hague Evidence Convention letter to Samsung in South Korea so Apple can pull documents for its U.S. antitrust case. Paperwork, sure. Also leverage. The kind that makes a process look “neutral” while it quietly decides who can reach what.

Apple wants a Hague Evidence letter to get Samsung documents

In its memorandum in Apple Inc. Smartphone Antitrust Litigation, Apple asks for a letter of request under the Hague Evidence Convention to Samsung Electronics in the Republic of Korea. The filing lays out the snag: Apple subpoenaed Samsung’s U.S. subsidiary, Samsung Electronics America, but Samsung’s U.S. team said the relevant records are at the Korean parent, not stateside. So Apple wants international cross-border paperwork to do the heavy lifting.

Apple describes the evidence it is after, including internal business reports and market analyses for Samsung’s smartphone and smartwatch businesses. That includes information on pricing, sales, competitive assessments, market shares, consumer demand, and switching. Apple also points to app-store materials: Galaxy Store documents, developer agreements and terms, license agreements, app review guidelines and tools, and documents tied to rival products and features that regulators and the alleged competition fight say matter. The filing also references digital-wallet and app ecosystem areas, including Samsung Pay, messaging, cloud gaming and streaming, companion apps, and policies about super apps and mini-programs.

Who benefits when the court becomes an international data courier?

Discovery is the arena, but reach is the real edge. When big tech can chase documents across borders, the side that can access more relevant records gets better fire. Apple is not only trying to build a record. It is trying to access the places where the details are stored.

The U.S. antitrust fight is United States v. Apple Inc., with related actions in the same district and a multi-district track. The government alleges Apple used app distribution rules, developer restrictions, and control over key iPhone features to limit competition. In the back-and-forth, both sides are playing games. Apple wants Samsung’s “home kitchen” paperwork, where the records Apple says it needs live.

Hague letters: the slow burn that looks polite on paper

The Hague Evidence Convention is meant to request evidence abroad in an orderly way. But the process can act like a delay machine. Discovery can take forever, and every step adds pressure that some parties can feel more than others. Apple may present its request as tailored and necessary, but the path is still part of the battlefield.

America angle: access, markets, and the gatekeepers in between

In tech, “speech” is not only what you say. It is where you can reach people and whether a platform can tilt the playing field while calling it moderation, safety, or compatibility. In an antitrust discovery fight, the argument includes documents and market structure, but it also involves the practical levers that decide who wins.

So keep an eye on what the court does next. If the letter request is granted and Samsung fights it, the wrangling continues. If it moves more smoothly, the case still turns on years of analysis about platform power and market dynamics. Either way, this is a reminder that tech freedom is not guaranteed by slogans. It is fought for in filings, subpoenas, and the fine print of access.

When big tech uses international evidence hoops to win a market case, who do you think really benefits: consumers or the gatekeepers?