Meta’s creepiest lawsuit in recent years will make you rethink its AI smart glasses


Meta’s Ray-Ban smart glasses are at the center of yet another controversy. A Kenyan AI training firm called Sama, which Meta used to help train its AI, saw its contract abruptly terminated shortly after its workers came forward with deeply troubling allegations (via BBC).

The workers claim they were repeatedly exposed to graphic content captured through Meta’s glasses, and now more than a thousand of them have lost their jobs.

The disturbing footage behind Meta’s AI training

Sama’s workers were data annotators, a role that involves manually labeling video content to teach Meta’s AI how to interpret images. They also reviewed transcripts of Meta AI conversations to make sure the chatbot was giving accurate responses.

What they didn’t sign up for, allegedly, was reviewing footage of people having sex or using the toilet, all filmed through Meta’s glasses without users’ knowledge. In one account, a man’s glasses were left recording in a bedroom, capturing his wife undressing.

Meta’s glasses do have a small indicator light that turns on when the camera is active, though that clearly hasn’t prevented misuse. The company admitted that contracted workers may occasionally review content shared with Meta AI, framing it as standard practice for improving user experience.

Why did Meta pull the contract?

Less than two months after those accounts surfaced, Meta terminated its agreement with Sama, leaving 1,108 workers without jobs. Sama says it met every standard Meta required and was never told otherwise. However, Meta disagrees, saying Sama fell short of its expectations.

A Kenyan workers’ organization believes the real reason was to silence staff who had gone public about humans reviewing smart glasses footage.

The UK’s Information Commissioner’s Office called the situation “concerning” in a letter to Meta. Additionally, Kenya’s data protection authority opened a formal investigation.

This isn’t Sama’s first difficult encounter with Meta. An earlier Facebook content moderation contract ended in similar controversy, with former employees describing exposure to traumatizing content.

Sama later said it wished it had never taken that work on. With regulators now circling and a legal case ongoing, the pressure on Meta to explain its decision is only growing.

Meta’s smart glasses have a much bigger privacy problem

Meta’s smart glasses are moving deeper into controversy as reports suggest they could soon identify people in real time. That has intensified privacy and civil rights concerns around face recognition in everyday public spaces.

Civil rights groups are pushing back against the idea citing that always-on identification could happen without clear consent.

Apps like Godsend are emerging in response to that threat, warning people when nearby smart glasses might be secretly recording them. That shows how uneasy people have become about being filmed without knowing it.

The technology is also showing up in less flattering ways, including reports of students using smart glasses to cheat in exams. That has added a new layer to the debate around misuse.

That said, it’s not all bad. The glasses have found genuinely good uses too, particularly in helping visually impaired people navigate spaces with assistance from strangers.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link