Apple changed macOS privacy settings to prevent third-party developers from misusing full-disk access to reach message histories. The move came about two weeks after Jason Aten reported that Meta’s AI agent Muse sent an unsolicited notification referencing a Messages thread. Going forward, those permissions will be constrained so apps can’t access message history via the prior configuration unless users explicitly configure access through the intended settings.
Apple announced it is tightening macOS “Full Disk Access” permissions after AI agents increased the risks of apps reading users’ files and messages. Apple cited that it will require “very explicit user action” before an app can be granted that level of access. As a result, users should face stricter, clearer prompts before allowing desktop AI agents to reach mail, messages, and browsing history.
The podcast episode reports on a massive FBI hack that 404 Media says exposed data tied to FBI employees and their spouses. The breach involves data on all FBI employees and their spouses. The episode then pivots to how some police surveillance data is being pitched for facial recognition and discusses Meta’s Muse agentic AI, including the role of humans in tasks.
Worldcoin’s Orb and World ID verify unique humans for online sign-ins and apps, with the World project described as also supporting bot-free messaging and payments via World Chain. The article says World ID is integrated across applications in 160 countries worldwide. It argues that a possible Worldcoin–OpenAI collaboration could help distinguish AI agents from humans and reduce bot-driven accounts and fake content risks in Web3.
Apple will add new limits on Macs’ “full disk access” feature in response to risks posed by AI agents. The change is being rolled out on Friday. Users can grant that level of access only after very explicit user action, tightening the permissions that apps can request.
Google announced a TEE-based federated learning system that uses Trusted Execution Environments to let third parties verify and audit data anonymization and training logic while limiting what operators can see. The company says Gboard training for next-word prediction models previously took 1–2 months per model, and with the new system it achieves speedups that are limited by TEE resource availability. The shift changes the threat model by reducing reliance on trusting the server operator, while moving gradient computation scheduling and improving training accuracy and compute time via TEEs and public transparency logs.
NetApp and Iterate.ai announced a partnership to run private generative AI using enterprise storage with the AIPod Mini appliance. The setup includes more than 200 agent templates, more than 200 skills, and access to more than 800 tools. As a result, more enterprises can move from pilots to production deployments that keep model and data within their own environment while agents deliver measurable business outcomes.
Bevel launched eu/jev as the second launch from the company, offering a Jev-like System One model hosted in the EU for users blocked by GDPR and data sovereignty limits elsewhere. It runs on Hetzner GPUs in Germany and matches Jev’s pricing, with free output tokens. The result is a GDPR-compliant way to call a Jev-style model without storing prompts or answers.
Every AI story that matters,
in your inbox by 8am.
TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the
day in two minutes. Follow companies and topics for alerts, or get the
briefing in Slack. Free, no spam, unsubscribe anytime.
Reading TLDRocket needs no cookies, and the readership counts we rely on come from
our own cookieless analytics. Google Analytics is the exception: it sets cookies and
reports to Google, so it stays switched off until you allow it. You can change your
mind any time from “Cookie settings” in the footer.
Strictly necessary
Session security and form protection (tldrocket-session,
XSRF-TOKEN, 2 hours). The site cannot work without them,
so they need no consent.
Always on
Google Analytics 4 (_ga,
_ga_<id>, up to 2 years). Measures which
stories and sections readers use. Google acts as a third-party processor and may
store the data outside the EU. No advertising, no profiling, no data sold.
