
Welcome to Techlore 🔐 This is where you'll learn about digital rights, privacy, security, digital control, and other important topics to push the world towards a safer internet. Here's everything you need to get started 🧵

Your digital life is being decided for you. Techlore helps you take it back—privacy, security, and digital rights, made simple by Henry Fisher.

Welcome to Techlore 🔐 This is where you'll learn about digital rights, privacy, security, digital control, and other important topics to push the world towards a safer internet. Here's everything you need to get started 🧵

👀
Coming soon to React Native! High performance desktop apps built with React Native GPUI.

Metal Cake Wallet branded Visa cards! Coming soon!

.@TechloreInc's founder Henry sat down with Ledger CTO @P3b7_ at @Ledger OP3N to talk about Ledger Atom: what it actually protects, where it stops, and what it means for privacy. Watch the full interview: youtube.com/watch?v=roTqSLSU…

They watch you. They force AI on you. They ship slop over stability. They hold your data. Then they lock you out of it. Today’s apology probably won’t be the last. It's never been cooler to leave big tech
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services. This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions. Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration. We will provide a full post-incident report once our review is complete.

Going live at the top of the hour 🔴 Techlore Office Hours starts at 10am pacific. Jump in, bring your questions, and let's have some fun! youtube.com/live/ImC31pdwt3k



Update: Fireworks CTO says Notion’s FAQ is wrong: Notion used the Batch API, which isn’t ZDR. Notion says it had a contractual ZDR commitment. Either way: ZDR has carve-outs even Notion missed, and users chats got stolen in the gap. Bad look either way.
This FAQ doesn’t accurately reflect the facts. Fireworks Inference API is ZDR (no retention, no training) and hasn't been affected by the incident. Batch API (used here) is *not* ZDR because it requires uploading a dataset first, before starting a batch job later. The user can explicitly delete the dataset if desired. Until it's deleted, the dataset is visible on the platform and can be downloaded. This= is explicitly documented in the docs: docs.fireworks.ai/accounts/z…. It’s also pretty obvious from the API design: dataset upload is a separate endpoint. This design is consistent with other inference providers, e.g. OpenAI: help.openai.com/en/articles/…

Apparently the “core privacy problem” with face cameras is that people don’t like face cameras. Have they considered not making face cameras? cnn.com/2026/11/12/tech/goog…

Australia has written a law that could make you prove your age to open your own inbox. Google told the Senate the Digital Duty of Care bill could force age checks on Gmail and Drive and lock out everyone under 18. The September draft protected privacy. The government deleted that part. reclaimthenet.org/google-war…

The best you can do right now: - Look for providers you can somewhat verify (attested, confidential inference) - Run locally - Don't paste secrets in a chat We have some suggestions, though I'd expect some changes soon in light this: tools.techlore.tech/#ai-a-ll…

If the concept of "ZDR" is any critical part of your workflow, it's time to rethink it. Currently looking into other options like @TinfoilAI @AskVenice @brave who are building some layer of hardware assurance in their privacy promises.

This should be a *massive* wake up to not just companies, but individuals relying on ZDR as some kind of proof that something is private. *zero* data retention is a big claim, and Fireworks, a well trusted service, showed how terribly they stuck to it.

As wild as Notion's response was, the real story here is Fireworks: a provider that sells itself on keeping your data private, couldn't stick to their promise. It's a bad look for the whole 'ZDR' industry. This is a reminder: ZDR is a promise, not a guarantee!

So two groups were exposed: a slice of Notion AI users (under 1% of workspaces) whose chats went through the Insights feature, and Fireworks own customers who stored secrets, datasets, models or billing info there.