"Decentralized Drupal: The decoupled Drupal endgame"
summary
Argues that decoupling Drupal is only step one toward a decentralized web and proposes concrete changes: decorate API responses with consumer permissions and expiry, implement field-level permissions that travel with content, and treat user storage as local data pods with interoperable APIs. Notes existing tools (REST, OAuth2, GraphQL, Solid) and tradeoffs: distributive hosting improves control but hurts discoverability; blockchain is optional for ledgers; cites 2016 ad market concentration (≈$0.85 of ad dollar to Google/Facebook) as motivation.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:08What we'll cover
- 7:12Web prehistory
- 8:23Examples of the open web
- 10:10Risks of centralization
- 19:04The decentralized web
- 20:24Key issues
- 22:57End users become data owners
- 24:33Interfaces become queries
- 25:28Decentralized Drupal
- 34:55Authorship and attribution
- 35:33Compensating contribution
related talks
39mAdventures in APIs
30mThe Time for Decoupled Drupal is Now
28mDecentralization & Web 3: What's Next for Users & Their Data
52mShould We Decouple?
33mRe-Decentralizing the Web and recapturing our data
40mGiving the individual control of their data: Open Source Decentralized Web Nodes
16mRefactoring the Web
54mDecoupling Patterns, Services and creating an enterprise level editorial experience