Its XML which requires a more difficult tree abstraction instead of a mapping/list abstraction
and the XML wraps html-formatted articles, so unless you hate yourself, you'll need to be embedding a browser for rendering, which means bundling a browser too (even on certain browser embed providing platforms like win32, since it still uses IE11 as its browser embed)
of course its easy to generate RSS.
- - -
and thats nevermind the whole impossibility of getting all articles without a daemon on a separate server, especially for high-volume feeds
Its XML which requires a more difficult tree abstraction instead of a mapping/list abstraction
and the XML wraps html-formatted articles, so unless you hate yourself, you'll need to be embedding a browser for rendering, which means bundling a browser too (even on certain browser embed providing platforms like win32, since it still uses IE11 as its browser embed)
Though I get the feeling google's approach of trying to desensitize me (emailing me about how great I am for traveling to mcdonalds like a slob, and gamifying my use of google maps, for example) instead of shamefully hiding it, is a fair bit worse
I wouldn't say worse per se, but it is bad in its own right for the reason the parent comment stated.
If it's "normal" to track every step and shove it in your face, surely you must be paranoid to not let them do at least some of that stuff.
I'm not saying there's no use for the data, and the services provided. It's just the opt-out nature of invading my privacy that I personally don't approve of.
I think he means the end result is worse. By being constantly shown the information you get desensitized to it. After years of that, you're much less likely to oppose this type of tracking than you would be had you never heard about it.
That doesn't really make a difference. Opt-out is essentially the same as just forcing it. The vast majority of users will never even know that they could be opting out.
IIRC, you're properly asked, the first time you try to do something, whenever you want to enable relevant tracking - e.g. share location history (e.g. when trying to set up "show my location"), or save voice data on Google servers (e.g. when setting up voice unlocking), etc etc.
I'm not exactly sure about app history and in-app search, though - just honestly don't remember about it. But it could be that user is actually asked at account setup time.
Point is, for many things Google actually properly asks for permission. Guess, it works for them, because timing's relevant. (They probably have ton of invisible tracking as well.)
Is that true? You can turn off your ability to see your activity history in Google, but does it actually delete (or not send?) any data from Google's servers?
Apparently there's a feature in the Google Home Mini that allows you to long press on the speaker to bypass the hot word detection ("Ok/hey Google"). Apparently there was a bug on this feature and random sounds could activate the listening of the Home, so it was recording data all day long.
Doesn't that just make the program opt-in instead of opt-out?
(And it separates the ActiveX stuff from the application too, which I'm happy to hear, applications that use it for decoding now shouldn't require the full WMP install)
Search your start menu for "Add Feature". There are lots of features not installed by default but part of Windows and still supported. They're not installed by default either because they're very obscure or specific functions not everyone uses (e.g. IIS, XPS). Or they're things Microsoft would like to kill off but can't because they're so entrenched (e.g. Active X, WMP).
problem is, having unimpeded speech online requires being harbored by private companies, as there really isn't much in terms of government-managed domains, government-managed DDoS protection, etc
DRM will exist with or without EME, and web-based distribution of major popular media will use that DRM in whatever form it takes. So EME versus no EME is a wash there, and I've argued at length that killing DRM cannot be done via "principled stands" -- it has to be done via market forces, as it was with online distribution of music.
Meanwhile, the rhetoric I was responding to was very much of the "people who only 99.99999% agree with me will be first against the wall when the revolution comes" school of thinking.
Exactly so there was not need to include it in the Standard
>and web-based distribution of major popular media will use that DRM in whatever form it takes.
Lost of popular media does not use DRM at all
>and I've argued at length that killing DRM cannot be done via "principled stands"
No it can only be done by principled stands
>it has to be done via market forces, as it was with online distribution of music.
That was killed by a principled stand not by market forces, the record labels wanted DRM, consumer did not give a shit, a few companies made a principled stand to say no...
That said, even if you want to claim it should be market forces that dictate DRM, then let the market decide by not ham fisting it into a Standard for HTML5.
That distorts the market and is the exact reason MS, Google and Netflix wanted to ensure it was in the Standard so they would not have to explain to the market why the DRM was there, why X device did not work with their products or have to compete in the market place on DRM or no DRM. DRM is "standard" now so there is no market competition for it.
I love all the DRM supporters (which you clearly are despite your claims to not be) that say "DRM was inevitable and putting in the standard would not change anything" Well then why put it in the standard? If it does not change anything, if it does not change the market, if having it in the standard is pointless why did MS/Google/Netflix/MPAA fight so hard to get it in?
because it does in fact matter. It does in fact change the market, and the conversation. Something being a "Standard" normalizes it in the market, allowing it to deployed faster, easier and with less consumer backlash. That was the entire point of the EME Spec, to normalize DRM to the consumer to make it less controversial, and more palatable
That was killed by a principled stand not by market forces, the record labels wanted DRM, consumer did not give a shit, a few companies made a principled stand to say no...
Apple introduced a large legal online music store with DRM. Apple got huge. Huge enough that record labels got scared and needed to break Apple's position. They turned to Amazon to start a competing music store, but had a problem: they needed to have the music from Amazon play on devices from Apple, or else people wouldn't shop at Amazon's music store. Since Apple probably wouldn't license Apple's DRM (since, after all, it would be for someone to break Apple's market position), the only option left was DRM-free. And lo and behold, Amazon became the first big music store with major-label music available DRM-free. And once there was one DRM-free store, it became hard to argue, from a market perspective, that there should be any that weren't. So Apple's ended up DRM-free too!
Market forces. Not people taking stands on principle.
That said, even if you want to claim it should be market forces that dictate DRM, then let the market decide by not ham fisting it into a Standard for HTML5.
The fact that you keep claiming EME is DRM tells me that you either don't actually know how EME works or what it does, or that you are willfully lying about it. Which is it, please?
I love all the DRM supporters (which you clearly are despite your claims to not be)
And here we are, back at the assertion that anyone who differs from your position by even a tiny amount must actually be 100% your enemy in every way. This is the kind of thinking that the twentieth century taught us to be very careful around, because it tends to lead to lots and lots and lots of dead bodies, all of them people who were "guilty" of being insufficiently perfectly compliant with the stated ideal.
>>>>Apple introduced a large legal online music store with DRM. Apple got huge... Huge enough that record labels got scared and needed to break Apple's position. They turned to Amazon to start a competing music store,
ROFL.... That is ... wow... Nothing about that is factually accurate, to state the Record Labels was the driving force behind DRM free Music...
Ummm No...
>>>The fact that you keep claiming EME is DRM tells me that you either don't actually know how EME works or what it does, or that you are willfully lying about it. Which is it, please?
The fact you believe EME has any other purpose except DRM tell me you do not actually know the purpose of EME, or what is does.
I'm not saying the labels wanted to go DRM-free. I'm saying that it was the only option they had at that point. They got legitimately scared of Apple's dominance in the market, and the only way to introduce a viable competitor was to do what they did with Amazon and a DRM-free store.
And just for the record, responses like "ROFL" and calling things "moronic" (as you did in your other comment) don't really make you look like you know what you're talking about or like you're someone who should be taken seriously.
It was not the only option that had, nor did they desire in any way to go DRM free, they had to be forced into it by both Amazon and Apple.
And just for the record, responses like your revisionist history, and Hyperbolic non-sense don't really make you look like you know what your talking about or like you're someone who should be taken seriously
(The webextension might be in beta? When I installed it a month ago it was in "beta" and had to be installed directly from their site, idk if they've uploaded it to the store yet)
"I’ve heard a few reasons:" ... that you've considered, then cherry picked two of them, so you can confirm your views?
To properly reason why the approach is wrong, shouldn't you consider all significant reasons, including backwards compatibility as probably the biggest one?
"New language that learns from the mistakes of languages before it" would generally be better than "language and runtime that is keeping compatibility with a programming language that was heavily rushed just to fill a feature point for a web browser"
One might as well state that the grass is green and sky is blue, no?
and the XML wraps html-formatted articles, so unless you hate yourself, you'll need to be embedding a browser for rendering, which means bundling a browser too (even on certain browser embed providing platforms like win32, since it still uses IE11 as its browser embed)
of course its easy to generate RSS.
- - -
and thats nevermind the whole impossibility of getting all articles without a daemon on a separate server, especially for high-volume feeds