| I agree. One time he (or she) is against that, another time he acts cocky like saying they'll now sabotage opera too (after being told it has a built in ad blocker) or bringing up existing DRM in a tone that is less like being sad those ideas are getting into web and more like he wants the same in html. It also starts reasonably with just focusing on chrome and then goes to asking google for a html drm, asking google to help sabotage chromium users, blocking firefox using obfuscated 10 mb js even though the site works well on ie8, vague threats of html drm coming soon to end ad blocking in an accusatory tone, saying they do all this to cut costs because each page they send is 3 megs and ff users are freeloaders, etc. Plus the weird title ('should we support' vs. 'we sabotage'), going with this to reddit instead of anonymously tipping fsf, eff or mozilla off (if he's already willing to leak that info and the fact he works there, the latter could remain hidden if he tipped these orgs off), etc. Edit: oh, and since css and images are loaded via js (on which he also comments by saying that people using no script 'ironically make their job easier') wouldn't that 10 mb one cause a flicker (fast internet) or a broken website for several seconds (slow internet) during at least the first load uncached load? And 2-3 megs of content for the few freeloading ff users is too much or can't be cdn'd but pushing that 10 meg js to everyone and taking up time of web devs and business-y people (for lobbying for drm at google or wherever) is fine and cheaper? |