Regulatory compliance in decentralised environments
summary
Argues that Matrix architecture maps onto DSA categories so home servers = hosting and clients = mere conduit, while managed hosting keeps immunity but retains obligations; flags end-to-end encryption as a blocker because server admins lack visibility for moderation and decentralized room moderation creates legal exposure. Describes practical responses: adapting trust-and-safety tooling, publishing a blog series, and industry lobbying via a coalition of 50+ members. Notes scale gap against platforms — example: Meta: 17 staff €8M devoted to the DSA.
AI-written summary · about
chapters (15)
- 0:00Introduction by host
- 0:23Speaker introduction
- 1:05Defining regulatory compliance
- 2:31Challenges in decentralized compliance
- 6:24Costs and complexities of compliance
- 7:09Element’s public policy strategy
- 9:14Collaboration in policy advocacy
- 11:20Digital Services Act overview
- 13:29Matrix’s DSA compliance approach
- 16:20Trust and safety adaptations
- 18:07Balancing DSA with GDPR
- 19:33Q&A begins
- 19:55Geographic compliance dilemma
- 22:06GDPR industry impact
- 24:55Closing remarks
related talks
13mRethinking Decentralised Governance
08mDeFi & Law: What Regulation Should and Shouldn’t
01h 01mRegulation through Governance
21mGlobal Regulation in a Decentralised World: The New Paradigm - What to Expect?
21mCompliance for AI and crypto security first
01h 04mRegulatory Incentives Towards Decentralization
01h 16mEnforcing Digital Regulation in Times of Omnibus
01h 10mResponding to Digital Responsibility Turning Entropy into Governance