Session CTO Kee Jefferys to discusses their decentralized messenger that uses private routing by default, requires no phone number, and runs on a network of thousands community-operated nodes. We dive deep into the technical decisions behind Session, including why they chose decentralization over perfect forward secrecy and how they're building a trustless messaging platform.

🔗 SOURCES & LINKS
• https://getsession.org/
• https://www.linkedin.com/in/kee-j-090502157/

⏱️ TIMESTAMPS
00:00:00 INTRO
00:02:21 WHY SESSION WAS STARTED
00:04:12 THE TEAM BEHIND SESSION
00:05:30 SESSION USER THREAT MODELS
00:09:20 REGISTRATION & USER ID
00:13:07 IS KEY VERIFICATION UNNECESSARY?
00:14:58 ONION ROUTING
00:16:53 USING THE OFFICIAL TOR NETWORK?
00:17:57 WHY NOT TOR?
00:19:15 HOW DECENTRALIZED IS SESSION?
00:21:07 ARE NODES TRUSTLESS?
00:24:53 HOW SESSION HANDLES METADATA
00:27:28 WHAT CAN SESSION HAND OVER?
00:29:20 SESSION + BLOCKCHAIN
00:31:24 IS ENCRYPTED DATA STORED?
00:33:58 REASON FOR THE SWARM
00:34:55 WHY 7?
00:36:26 SESSION LOGIN & ACCOUNT RECOVERY
00:39:17 BACKUP & RESTORE
00:40:57 PFS (PERFECT FORWARD SECRECY)
00:46:56 IS SESSION A SIGNAL FORK?
00:48:10 USABILITY PROGRESS
00:52:58 DEVICE LINKING
00:54:25 CUSTOM NOTIFICATIONS/UNIFIED PUSH
00:59:25 ANDROID NOTIFICATIONS + BATTERY
01:02:34 SESSION'S BUSINESS MODEL
01:05:48 ENCOUNTER WITH LAW ENFORCEMENT
01:12:55 ARE THERE APP STORE PROTECTIONS?
01:16:58 WHAT'S NEXT FOR SESSION?
01:19:41 FAVORITE PRIVACY PROJECT?
01:22:41 OUTRO

🎥 VIDEO
Watch on YouTube