And they tell you this is happening. The links I shared illustrate Google and Mozilla doing things without asking or informing the user. Apple do indeed have form in this area too, battery/processor throttling springs to mind.
With regards maps, although what this has to do with your original question is beyond me, Apple informed the user very clearly on where the data is from and what data they were collecting, they still do. It was originally a combination of TomTom and OpenStreetMap, by the way.
Also, Jobs was pushing privacy in 2010 - "Privacy means people know what they're signing up for, in plain English and repeatedly. I believe people are smart and some people want to share more data than other people do. Ask them. Ask them every time. Make them tell you to stop asking them if they get tired of your asking them. Let them know precisely what you're going to do with their data."
I agree that companies can change. Big companies rarely do. I'm concerned that it's only a matter of time before Mozilla make the decision to switch to blink, which would be the end for them and the open web.
Interestingly, of the complaints made in this article, 6 are Editors Drafts, not agreed upon standards, or Working Drafts, again experimental un-agreed 'standards'. I'll concede that a working draft is close enough to being standardised. The rest, bar one, are implemented in WebKit. So the complaint in the article is that the WebKit project is holding up the web by not including Google's experimental features in a bid to say Apple should be allowing other, less secure rendering engines on a platform where users store a ridiculous amount of PII. It's being framed as 'freedom' - I'm sceptical. They'll be caterwauling about 'choice', but by enforcing 'choice', there is very real, and frankly sinister, risk that it will be lost irrevocably along with any semblance of an open web. Careful what you wish for.
With regards maps, although what this has to do with your original question is beyond me, Apple informed the user very clearly on where the data is from and what data they were collecting, they still do. It was originally a combination of TomTom and OpenStreetMap, by the way.
Also, Jobs was pushing privacy in 2010 - "Privacy means people know what they're signing up for, in plain English and repeatedly. I believe people are smart and some people want to share more data than other people do. Ask them. Ask them every time. Make them tell you to stop asking them if they get tired of your asking them. Let them know precisely what you're going to do with their data."
I agree that companies can change. Big companies rarely do. I'm concerned that it's only a matter of time before Mozilla make the decision to switch to blink, which would be the end for them and the open web.
Interestingly, of the complaints made in this article, 6 are Editors Drafts, not agreed upon standards, or Working Drafts, again experimental un-agreed 'standards'. I'll concede that a working draft is close enough to being standardised. The rest, bar one, are implemented in WebKit. So the complaint in the article is that the WebKit project is holding up the web by not including Google's experimental features in a bid to say Apple should be allowing other, less secure rendering engines on a platform where users store a ridiculous amount of PII. It's being framed as 'freedom' - I'm sceptical. They'll be caterwauling about 'choice', but by enforcing 'choice', there is very real, and frankly sinister, risk that it will be lost irrevocably along with any semblance of an open web. Careful what you wish for.