







To avoid lock in, you need the ability for the user to credibly exit.
Exit Chat Control · Become Ungovernable
A practical field guide to escape Chat Control and reclaim your digital privacy: encrypted messaging, email, VPN, DNS, passwords, Linux, GrapheneOS, self-hosting. Free, open source, no tracking.


Introducing Automatic Key Verification
Signal now offers a feature called “automatic key verification” which complements the existing safety number system. Signal is always end-to-end encrypted, and automatic key verification provides an additional, streamlined way to confirm that there’s no unexpected party between you and the other ...

OpenAI unveils Lockdown Mode to protect sensitive data from prompt injection attacks | TechCrunch
Even with Lockdown Mode, ChatGPT could be vulnerable to prompt injections, but the goal is to reduce the likelihood that sensitive data gets shared in the process.

I don't like passkeys | Ethan Hawksley
Why passkeys are a step back for personal security: examining account lockout risks, platform lock-in, hardware key limits, and fragile recovery flows.

Trust & Safety Library - Trust & Safety Professional Association
Welcome to the Trust & Safety Library! We use this space to collect articles, blog posts, journal articles, lectures, podcasts, and websites that trust and safety professionals may find useful in developing policies, supporting moderators, building systems to detect violations, and generally deepening their practice. We welcome your submissions and feedback. This project was initially


DropLock
The link below is like an open lock box that belongs to you. Anyone you share it with can put a secret inside and create a locked link that only you can open.

Safety Without Compromising on Privacy
Our approach to safeguards in Tinfoil Chat that keeps your conversations private: model evaluations before hosting, plus safeguard models that run exclusively inside secure enclaves.

Landlock: unprivileged access control — The Linux Kernel documentation
The goal of Landlock is to enable restriction of ambient rights (e.g. global filesystem or network access) for a set of processes. Because Landlock is a stackable LSM, it makes it possible to create safe security sandboxes as new security layers in addition to the existing system-wide access-controls. This kind of sandbox is expected to help mitigate the security impact of bugs or unexpected/malicious behaviors in user space applications. Landlock empowers any process, including unprivileged ones, to securely restrict themselves.
don't think i'm worried about this in particular, but it does make me wonder what exactly is the credible exit for my own data if a space authority becomes malicious and stops issuing me credentials? (still wrapping my head around the permissioned data proposal so sorry if this is a dumb question!)
Andrew Lisowski 💻
I really worry that permissioned data is gonna kill a lot of stuff Take my recipe app: If i wanted no one to have access to the records but my app all i have to do is 1. create a space 2. use that space for all user content Bam, now no open data
Wondering if using "credible exit" when talking about atproto will confuse/mislead people how atproto works under the hood?
𝕮
This is a radically different idea than the advocacy I’ve seen for “data portability” and ”data sovereignty”. It’s a *restructuring* of power rather than small adjustments to existing structures. atproto and local-first, both in their own ways, demonstrate what such a restructuring can look like.