Urgent.News

What's breaking now, across thousands of outlets.

Tech

A jury found Facebook guilty of 43 million privacy violations, and Meta could owe billions

The New Mexico Department of Justice recently announced a landmark decision from the jury in the State of New Mexico v. Facebook, Inc. case. Meta's social network was found guilty of violating the New Mexico Unfair Practices Act (UPA) more than 43 million times, providing misleading statements to local consumers... Read Entire Article

A jury found Facebook guilty of 43 million privacy violations, and Meta could owe billions

A New Mexico jury has found Facebook guilty of 43 million violations of the state's Unfair Practices Act, resulting in potential billions of dollars in penalties. The verdict stems from the Cambridge Analytica scandal, one of the largest privacy breaches in history. Meta, the parent company of Facebook, is accused of misleading consumers about its data practices.

Despite settling the Cambridge Analytica class action, Meta continues to face privacy abuse allegations. New Mexico Attorney General Raúl Torrez emphasized that the verdict sends a message that rules apply to everyone, including Big Tech firms. The jury found Facebook lied to New Mexico residents about data management and violated unfair and deceptive practices laws.

The company is also accused of profiting from misinformation and hate speech while claiming to combat it. Facebook has stated that its platforms are protected by First Amendment rights but will fight the verdict. The judge will now determine the exact amount Meta must pay, with the maximum penalty reaching $5,000 per violation.

Written by urgent.news from TechSpot's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at techspot.com →

More in Tech

A shipping exception queue that ages, deduplicates and can be claimed

Most ecommerce backends model shipments as a happy path with a status column. label_created → in_transit → delivered . When something goes wrong, the row gets stuck at whatever it was last stuck at…

  • Exception queue manages stuck shipments in destination depots
  • Shipmentexception table includes id, kind, dedupekey, and state columns
  • Dedupekey prevents queue growth from repeated webhooks

Introducing IdentiFlows.dev: A Visual Reference for Identity Flows

Every developer who has played with OAuth 2.0 or OpenID Connect knows this moment: you need to double-check the exact sequence of a flow, and the diagram you remember seeing is scattered somewhere…

  • Identity Flow Diagrams website offers visual reference for identity protocols
  • Eight flows covered: OAuth 2.0, OpenID Connect, SAML 2.0, WebAuthn
  • Future additions planned: OAuth 2.0 Client Credentials, OAuth 2.0 Device Authorization

A Practical Checklist for Debugging a Broken API Request (With Free Browser Tools)

You send a request. You get a 401 . Or a 400 . Or an empty response and a vague error. Most API bugs come from a small set of causes: a malformed token, bad encoding, wrong headers, or a network…

  • Reproduce request with cURL using -i flag for headers
  • Inspect status code for specific error meaning
  • Decode JWT parts to check expiration and audience

More from Wednesday 30 September →