MSC Workshop
summary
Live demo creates a concrete MSC that adds a copy_hint field to m.room.message content so clients can present or copy specific substrings (eg 2FA codes). The workshop edits a GitHub proposal template, pastes JSON examples, assigns MSC 4197 with an unstable prefix, and lands an Element Web implementation PR as proof of concept. Discussion surfaces alternatives (single string vs array, extensible-event mixin), security and redaction concerns, and the spec core review / FCP path that leads to merge.
AI-written summary · about
chapters (17)
- 0:00Introduction to MSC workshop
- 1:04Writing an MSC from scratch
- 10:08Drafting the proposal section
- 23:39Adding alternatives and issues
- 28:24Security considerations
- 31:02Publishing the MSC
- 35:57Community review process
- 40:17Handling feedback and iterations
- 45:42Unstable prefixes explained
- 51:08Implementation requirements
- 55:14Final comment period
- 1:02:24Spec PR and stable release
- 1:08:46Handling product feedback
- 1:27:24Spec team neutrality
- 1:33:08Foundation's role in implementation
- 1:47:15Barriers to MSC entry
- 1:56:40Q&A and closing remarks
related talks
23mBeyond Scraping: The Future of Web Data Access with WebMCP
45mModel Context Protocol (MCP): The future of user interactions?
21mMCP at 1. The state of the protocol you love (or hate)
20mWebMCP: Stop scraping the Web, start calling it
18mWeb Developer Security: Best Practices & Beyond
29mMCP Apps: Primitives, discovery, and the Future of Software
33mHooks with SMART messaging
12mBuilding Better Remote MCPs: Web3’s Answer to Auth & Monetization