End-to-end encrypted file sharing may sound simple, but for Cryptee, it took five years to ship. In this interview, Henry sits down with John Ozbay, founder and CEO of Cryptee, to talk through why: preventing CSAM, why client-side scanning doesn't work, how Cryptee's solution was designed to raise the barrier to mass spread without compromising encryption, and the broader philosophical question of where developer liability ends and moral responsibility begins.

🔗 SOURCES & LINKS
• Cryptee: https://crypt.ee
• Stop Chat Control: https://stopchatcontrol.eu
• Open Web Advocacy: https://open-web-advocacy.org
• EDRI: https://edri.org

⏱️ TIMESTAMPS

(00:00) - INTRO
(04:08) - E2EE SHARING HESITATIONS
(14:09) - HOW IS BIG TECH HANDLING THIS?
(16:24) - LOCAL SCANNING
(19:27) - HOW ARE CHAT APPS HANDLING THIS?
(21:24) - E2EE BACKUPS
(22:40) - HOW MUCH IS THIS CONSIDERED?
(25:38) - CRYPTEE'S SOLUTION
(42:09) - THREAT MODELING
(48:18) - MEGA'S APPROACH
(53:16) - LIABILITY VS. RESPONSIBILITY
(01:01:40) - HOW TO ENGAGE PRODUCTIVELY
(01:09:48) - CHAT CONTROL & ULTERIOR MOTIVES
(01:21:34) - IS CHAT CONTROL DEAD?
(01:25:33) - HOW JOHN GOT INVOLVED
(01:34:44) - CHANGING OVER TIME + RIGHT TO REPAIR + LINUX
(01:41:32) - CLOSING THOUGHTS

🎥 VIDEO
Watch on YouTube

🧡 SUPPORT TECHLORE
Keep Techlore Talks independent & growing: ★ Support this podcast ★

End-to-End Encrypted Photo Sharing: How Cryptee Balances Privacy, Abuse Prevention, and Legal Risk

Techlore Talks

End-to-End Encrypted Photo Sharing: How Cryptee Balances Privacy, Abuse Prevention, and Legal Risk