Comment on Muse privacy invasions are freaking out Meta staffers, internal chats show
You are viewing one comment and its replies. View all comments · View the comment above
You are viewing one comment and its replies. View all comments · View the comment above
Comments
I’m not saying Meta isn’t spying on users. I’m sure they are. But this doesn’t make sense as a symptom of spying.
If you want to spy on users you just record all their info. You absolutely don’t give the LLM they talk to access to that same information - that’s nearly useless, and is one of the surest ways to make sure the users find out. The LLM doesn’t need to know about the spying.
You’re assuming they’re not dumb af.
It’s both, and they are indeed dumb AF. Muse drinks from the same spying trough the rest of the slop platform sits on.
Where they’re being idiots is that the model is internally being fed a system prompt meant to foster “engagement” in between “sessions”, and it absolutely is being fed not just context beyond the scope of the task, but that context…
Is clearly being populated by another LLM model that is slurping from behind where the totally secure e2ee decode happens after the “private” message goes from Grandma Conspiracy Hoax’s inbox and through Aunt Zionist Shill onto Zuckerberg’s private masturbation window.
The second model doesn’t match the info against the specific user before passing it to the first, it passes the full search results it pulled and leaves the first model to determine relevant use.
Great shit if you’re running a tight local harnessing set up and don’t want to waste compute on your helpers sanitizing the a2a calls that the model handling orchestration would need to parse anyways.
Asinine and dumbfucked when your set up is a multi-user activity panopticon which your bottom line desperately relies on pretending isn’t the case.
They want their AI to know everything.
Sign in to comment. Sign in