As usual the headline over promises and under delivers. The program will continue after a review.

It came while morale at the company was at a nadir

At least there’s this. The first step to becoming better people is facing up to the global horrors your work is responsible for.

following fresh layoffs

Oh, never mind.

Fuck Meta always.

“We will only re-enable MCI when we are confident in the effectiveness of our data protection controls,” Stephane Kasriel, a Meta vice president overseeing AI research, told employees Monday, according to Wired. Kasriel said the company discovered and resolved the issue last week, but that the  initial fix didn’t work.

Temporary pause on the program. It will be back on by next week I bet. Also, at this this point, if you work for meta, it is getting harder and harder to feel bad for you.

while we have no indication at this time that any data was improperly accessed by Meta employees, we’re pausing it while we investigate

So why are you pausing it again?

we have no indication at this time that any data was improperly accessed by Meta employees

What does "no indication" mean if they record every keystroke? Did they screw up their snooping program as usual, or are they lying as usual?

Site asks to use cookies and access to private data.

I wish mods would ban sites like this. What's the point of discussing privacy on a forum with links that violate privacy?

The company, however, is poised to resume the data tracking program once the issue is settled.

Yep. Sounds like Meta.

My company (near the top of the fortune 500 companies) has been doing this for a while. They track every file change, intercept all http web connections using MitM attacks, etc.

It causes tons of issues for software development and the production application operations including extreme slowdown of both laptops and servers as it thrashes disks and pauses things when the buffers fill up. It can't keep up with applications that use lots of disk caching or make many small file modifications, like merging a large git repo. So things crash and generally run very poorly all the time. Plus all http connections end up with invalid certificates after the MitM attacks, and they block a lot of connections even to places like GitHub which we use. So things break constantly.

They laid off most technical people with any experience (should say with any moderately higher salaries) as part of their push for AI to take over those jobs. So, most of the people dealing with these issues don't understand the technology.

I can't imagine what they could use all pf that data for which includes tons of employee and customer private data. It would take years to sort through for some specific breach, so it's useless for it's stated purpose. It's just ripe for hackers to steal tons of data on tens of millions of people around the world, though.

When executives and middle managers are put on charge of technical decisions utilizing "AI" and short term, junior level technical contractors, it's no wonder they make tons of bad decisions and don't recognize how much it's costing them. If only there was competition to drive innovation rather than easy cost cutting like laying off experienced employees, maybe things would change. But that's impossible in the modern late-stage capitalist economy they've created. So we just have to wait for the whole system to collapse. But by then we may have reached a point where it's no longer possible to prevent extinction from climate change (water and food shortages, pandemics, and all the other things were seeing). We just need to wait and see what collapses first I suppose. If only democracy hadn't been turned into this farce and media hadn't been coopted and consolidated to not allow enough people to see what's really going on, maybe we could change it.

“We have carefully designed this program with privacy safeguards, and while we have no indication at this time that any data was improperly accessed by Meta employees, we’re pausing it while we investigate,” a spokesperson told outlets.

"Pwetty pweese, do not make ewows and pwotect the employee infowmation"

for employee in company:
  copy_information(employee.data, protected_folder)
  compress(protected_folder)

gEt OfF oF fAcEbO0K l0SeRs... be brave just say NO... fuck keeping in touch with grandmal. Just don't.... stop now. you fucking yankkkee pig dog narcissist. Fuck big teeeccchhhh

all we do is loser shit....

Seems like a great time to realize you work at one of the worst companies in the world, and leak all that discovered data to the press..

Man, I know Meta is too big to fail and all that, but this really reads like the company is falling apart...

I’m just imagining the keylogs for meta video editors looking like pages upon pages of

Lklk⇧cllllkjk⇧cvalk⇧clllllllkjjk⇧cv…

This is the inevitable consequence of the 'cloud-telemetry-first' approach to AI developer tools. If your AI coding assistants or workflow agents are logging your terminal history, active files, or screen activity back to a centralized cloud database for 'orchestration' or 'training,' you have essentially installed corporate spyware. It doesn't matter if it's Meta, Microsoft, or a startup—a single misconfigured pipeline or data breach will expose trade secrets, API keys, and private credentials. AI agents must have hard local boundaries. Tool execution (reading files, executing shell commands, querying local databases) must happen entirely locally under a zero-knowledge architecture, and every single execution must require explicit user-consent dialogs. Sending execution telemetry back to the cloud is a massive security hazard that corporations are only beginning to realize.

Seems like a great time to realize you work at one of the worst companies in the world, and leak all that discovered data to the press..

TLDR?