zlacker

>>pabs3+(OP)
It's a fine idea. But what I'm taking away from this post is the link to the Google/Chromium web DRM prototype and summary ... yikes. https://raw.githubusercontent.com/RupertBenWiser/Web-Environ...

>- The web page executing in a user's web browser

>- A third party that can “attest” to the device a web browser is executing on, referred to as the attester

>- The web developers server which can remotely verify attestation responses and act on this information.

Chome only for now but I imagine after it's pushed to Chromium and all the browser based on that Mozilla will implement it too (just like all the other DRM FF has now).

>>superk+ji
Google would do anything to make it harder for others to crawl the web. Killing RSS was part of that strategy.

News sites will implement these DRMs, but of course they will still allow Google because it is their source of traffic. Alternative search engines and good bots will be locked out.

>>fooyc+Km
>Killing RSS was part of that strategy.

Oh please.

I get that it's more satisfying to blame Google than the faceless masses who had zero interest in RSS and who had a variety of alternatives to Reader in any case.

I guess they also had a strategy to kill social media by axing Google+ and user-created encyclopedias by killing Knol.

>>ghaff+xA
Not only Reader, but also the RSS support in Chrome and Firefox (whose Google used to be the primary source of funds). And Feedburner.

>>fooyc+vF
> Firefox (whose Google used to be the primary source of funds)

Google deal with Firefox was always about being the default search engine there, and that's it. They never had any power of cutting it adding features to the project.

>>greisk+oJ
Officially, sure, but you shouldn't pretend that Google's funding isn't the main survival line for Mozilla as an entity, and that there isn't pressure there.