Linked by Thom Holwerda on Sun 17th Dec 2017 19:39 UTC
Mozilla & Gecko clones

For a long time, it was just setting the default search provider to Google in exchange for a beefy stipend. Later, paid links in your new tab page were added. Then, a proprietary service, Pocket, was bundled into the browser - not as an addon, but a hardcoded feature. In the past few days, we’ve discovered an advertisement in the form of browser extension was sideloaded into user browsers. Whoever is leading these decisions at Mozilla needs to be stopped.

Mozilla garnered a lot of fully deserved goodwill with the most recent Firefox release, and here they are, jeopardising all that hard work. People expect this kind of nonsense from Google, Apple, or Microsoft - not Mozilla. Is it unfair to judge Mozilla much more harshly than those others? Perhaps, but that's a consequence of appealing to more demanding users when it comes to privacy and open source.

Thread beginning with comment 652245
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:


It doesn't sync calendars with exchange worth anything... not really Mozilla's fault though.

You used to be able to use webdav, but this shows how dated my experience with exchange is. Apparently MS took it out it in favor of their own Exchange Web Services soap xml API.

The WebDav in the previous version of exchange has been replaced with Exchange Web Services (EWS) in the exchange 2010

Exchange Web Services - What You Didn't Know

“APIs that Will Be Removed” section in Exchange API-spotting
We have added a variety of features; such as ACL support and Public Folder access to Exchange Web Services in Exchange 2007 SP1 to replace Exchange WebDAV functionality and are continuing to invest in additional functionality in the next release of Exchange.

I guess it shouldn't be a big surprise, microsoft has a history of breaking interoperability standards.

Reply Parent Score: 2

darknexus Member since:

I guess it shouldn't be a big surprise, microsoft has a history of breaking interoperability standards.

Yep, even with their own software. Ever seen what happens when you try to connect Office 2003 to an Exchange 2010 server? Not pretty, and this was back in the day when people still ran Office 2003 for a variety of reasons.

Reply Parent Score: 2