How to Destroy the Web Opera
summary
A rapid checklist of tactics that actually break access: deliberately code only for WebKit (PPK poll showed 32% would prefer one engine), do browser sniffing and user‑agent spoofing, require specific hardware or ActiveX so Korea‑style e‑services exclude non‑Windows users, demand JavaScript or deliver an empty body + JavaScript app, replace real links/buttons with spans/div nests, break URLs with JS wrappers, geo‑block by IP, and enshrine no‑linking or single‑copy rules in terms to make content unusable.
AI-written summary · about
chapters (16)
- 0:00Introduction and humor
- 1:06Why destroy the web
- 6:06Coding for one browser
- 8:12Device and platform exclusivity
- 10:21Browser sniffing techniques
- 13:49Forcing app downloads over the web
- 14:51Mobile exclusion in emerging markets
- 17:25Requiring JavaScript and plugins
- 19:59Legal and political web censorship
- 25:04Excluding keyboard and screen reader users
- 27:14Misusing HTML for inaccessible elements
- 30:25Breaking the URL addressing system
- 31:06Restricting terms and conditions
- 35:29Content filtering and censorship
- 37:18The real cost of web destruction
- 40:23Q&A and closing remarks
related talks
48mHow to defend the web
59mBrowsers Gone Wild
36mThe Most Annoying Website (Aka "the Power of the Web Platform")
30mThe Most Annoying Website (aka "The Power of the Web Platform")
43mWhy Opera Needs WebKit, or Opium for the People
42mThe Perilous Future of Browser Security
55mWeb Application Security: Browsers Fight Back!
01h 18mMobile browser panel