summaryrefslogtreecommitdiffstats
path: root/speaker-notes
diff options
context:
space:
mode:
Diffstat (limited to 'speaker-notes')
-rw-r--r--speaker-notes22
1 files changed, 22 insertions, 0 deletions
diff --git a/speaker-notes b/speaker-notes
new file mode 100644
index 0000000..e793238
--- /dev/null
+++ b/speaker-notes
@@ -0,0 +1,22 @@
+Which apps use WebView?
+ A couple years ago, Jeremy checked all the PRISM Break apps to see which ones
+obviously used WebView. He doesn't have the exact numbers, but it was something
+like a third. Now it's a half. So WebView is becoming increasingly prevelant,
+and quickly.
+
+What's the matter with Chromium?
+ * Chromium manipulates its extension API to prevent extensions from blocking
+ads. They claim this is to prevent performance problems, which is a lie because
+Mozilla already solved those performance problems in production via a tiny
+tweak to the extension API that didn't impact ad blocking. Someone makes money
+when browsers cripple ad blocking, and it's not you the user.
+**Chromium is an antitrust violator and this harms the user's interests.**
+
+ * Chromium does everything in their power to prevent users from escaping the
+certificate authority system for TLS. Whether it's DNSSEC/DANE/TLSA,
+perspective verification, HPKP, manual key pinning, OS-level key pinning,
+or Namecoin, you can be pretty sure that if a mechanism exists to verify
+TLS certificates without fully trusting public CA's, the Chromium devs have
+tried to kill it.
+**Chromium is hostile to users' security.**
+