- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Feb 2013 12:55:26 +0000
- To: public-html-media@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21037
Bug ID: 21037
Summary: These extensions will make it harder to make money on
the web
Classification: Unclassified
Product: HTML WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: blocker
Priority: P2
Component: Encrypted Media Extensions
Assignee: adrianba@microsoft.com
Reporter: koraq@yahoo.com
QA Contact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-media@w3.org
A comment, as requested.
This RFC suggest extensions that as an idea is just horribly broken.
Using the HTTP protocol is an idiotic way to implement this. If you want to
secure the web, IP-SEC is the way to make sure you talk to the right server. If
you want to deliver specific data from a server to a client, use the
interpreter of that data to handshake and decrypt that encrypted data. Write a
god damned plugin for Chrome/Firefox that is needed for your content.
Using the protocol that delivers all kinds of data and locking it down for just
your use case is not only stupid, but also un-elegant and technically less
sensible.
Not only that.
In order to make the most money on the web, you need to get as many people on
the train as possible. Taking an open medium where people can connect freely
and in a simple way create and share content and limit is a bad idea. Browsing
1000 sites those people get exposed to hundreds of ads. The revenue from that
will dry up at once if the HTTP access way is limited to a single file
encrypted lane. You will all earn *less* money that way.
And this is "do no evil" in what way?
Scrap this junk.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 18 February 2013 12:55:32 UTC