5 ms·

I hate tracking like everyone else but what you wrote is just pure FUD. Apple forces Firefox/chrome to use their crippled engine but that has nothing to do wit

I hate tracking like everyone else but what you wrote is just pure FUD. Apple forces Firefox/chrome to use their crippled engine but that has nothing to do with the parts that do the tracking. For the record, Firefox has built-in anti tracker which is enabled by default and they do that on all platforms. And don't forgot the privacy enhancements Samsung added to their browser years ago.

deleted 7y ago
[deleted]
AsusFan 7y ago
> For the record, Firefox has built-in anti tracker which is enabled by default and they do that on all platforms Firefox's anti-tracking protection doesn't block google analytics by default. They only block "third party" cookies - which in practice translates as: Google's competition. The fox knows better than to bite the hand that feeds it.
- panpanna 7y ago
  Do you have a source for that? Firefox docs and disconnect don't say anything about this https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-android https://support.mozilla.org/en-US/kb/enhanced-tracking-prote...
  - exhilaration 7y ago
    https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Privacy/Tracking_Protection#What_does_this_mean_for_your_website https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Pri... The above specifically shows you to make sure your site continues to function when Google Analytics is blocked by Firefox. I can't find any evidence that Firefox doesn't block Google Analytics.
    - donclark 7y ago
      I highly recommend: https://addons.mozilla.org/en-US/firefox/addon/umatrix/ https://addons.mozilla.org/en-US/firefox/addon/umatrix/
- SmellyGeekBoy 7y ago
  I'm not sure where you got this idea but it's completely untrue.
  - otabdeveloper4 7y ago
    He's 100% correct. Google Analytics is a "first-party" cookie and thus not blocked by any privacy helpers. "Cookie blocking" and GDPR is just Google abusing its monopoly position, nothing more. Source: I work in adtech.
    - jeromegv 7y ago
      Mainly 1st party but some features might use 3rd party. -- For customers that are using Google Analytics' Display Advertiser features, such as remarketing, a third-party DoubleClick cookie is used in addition to the other cookies described in this document for just these features. For more information about this cookie, visit the Google Advertising Privacy FAQ. Source: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage https://developers.google.com/analytics/devguides/collection...
acdha 7y ago
Using “FUD” in one sentence and calling WebKit “crippled” in the next is not a good way to establish yourself as a rational analyst. Firefox is my primary browser but I don’t think advocacy like that is helpful.
- panpanna 7y ago
  3rd party browsers are forced to use a webkit engine instead of their own. By any definition, this adds a severe limitation => crippled. I also think (I could be wrong) safari has access to a slightly different webkit engine than third party browsers.
  - Retric 7y ago
    A forced choice is only a severe limitation if it’s significantly worse. That’s currently a guess as there are no iOS comparable options to consider at this point in time. Further, Google has a competitive interest in eventually crippling their iOS rendering engine.Then again I don’t use desktop Crome so that could be my bias talking.
    - AstralStorm 7y ago
      No, they wouldn't ever do that. That would be like making an anti-demo. Google has an interest in getting as big a market share for their browser as they can. In as much as disabling their web application functionality of you do not use chrome. Android is much less relevant than the browser. And this does not even begin to touch on Firefox. The problem is a policy one, with Apple really liking their walled garden and veto rights to any design.
      - Retric 7y ago
        Edit: I don’t think Crome has a better engine. For sake of argument lets’s suppose Android Crome was a 90 and iOS Crome is currently a 70 due to the rendering engine. In theory they could replace the engine and hit say 85 given enough resources. But, they could also replace the engine hit 75 and blame iOS. Their still demonstrating an improvement and intentionally crippling it at the same time. That said any such measurement is arbitrary. I personally like having a unified rendering engine because it’s less testing when developing mobile websites. There is no way to improve that situation by introducing a new engine.

deleted 7y ago

[deleted]

AsusFan 7y ago

> For the record, Firefox has built-in anti tracker which is enabled by default and they do that on all platforms Firefox's anti-tracking protection doesn't block google analytics by default. They only block "third party" cookies - which in practice translates as: Google's competition. The fox knows better than to bite the hand that feeds it.

panpanna 7y ago
Do you have a source for that? Firefox docs and disconnect don't say anything about this https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-android https://support.mozilla.org/en-US/kb/enhanced-tracking-prote...
- exhilaration 7y ago
  https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Privacy/Tracking_Protection#What_does_this_mean_for_your_website https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Pri... The above specifically shows you to make sure your site continues to function when Google Analytics is blocked by Firefox. I can't find any evidence that Firefox doesn't block Google Analytics.
  - donclark 7y ago
    I highly recommend: https://addons.mozilla.org/en-US/firefox/addon/umatrix/ https://addons.mozilla.org/en-US/firefox/addon/umatrix/
SmellyGeekBoy 7y ago
I'm not sure where you got this idea but it's completely untrue.
- otabdeveloper4 7y ago
  He's 100% correct. Google Analytics is a "first-party" cookie and thus not blocked by any privacy helpers. "Cookie blocking" and GDPR is just Google abusing its monopoly position, nothing more. Source: I work in adtech.
  - jeromegv 7y ago
    Mainly 1st party but some features might use 3rd party. -- For customers that are using Google Analytics' Display Advertiser features, such as remarketing, a third-party DoubleClick cookie is used in addition to the other cookies described in this document for just these features. For more information about this cookie, visit the Google Advertising Privacy FAQ. Source: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage https://developers.google.com/analytics/devguides/collection...

acdha 7y ago

Using “FUD” in one sentence and calling WebKit “crippled” in the next is not a good way to establish yourself as a rational analyst. Firefox is my primary browser but I don’t think advocacy like that is helpful.

panpanna 7y ago
3rd party browsers are forced to use a webkit engine instead of their own. By any definition, this adds a severe limitation => crippled. I also think (I could be wrong) safari has access to a slightly different webkit engine than third party browsers.
- Retric 7y ago
  A forced choice is only a severe limitation if it’s significantly worse. That’s currently a guess as there are no iOS comparable options to consider at this point in time. Further, Google has a competitive interest in eventually crippling their iOS rendering engine.Then again I don’t use desktop Crome so that could be my bias talking.
  - AstralStorm 7y ago
    No, they wouldn't ever do that. That would be like making an anti-demo. Google has an interest in getting as big a market share for their browser as they can. In as much as disabling their web application functionality of you do not use chrome. Android is much less relevant than the browser. And this does not even begin to touch on Firefox. The problem is a policy one, with Apple really liking their walled garden and veto rights to any design.
    - Retric 7y ago
      Edit: I don’t think Crome has a better engine. For sake of argument lets’s suppose Android Crome was a 90 and iOS Crome is currently a 70 due to the rendering engine. In theory they could replace the engine and hit say 85 given enough resources. But, they could also replace the engine hit 75 and blame iOS. Their still demonstrating an improvement and intentionally crippling it at the same time. That said any such measurement is arbitrary. I personally like having a unified rendering engine because it’s less testing when developing mobile websites. There is no way to improve that situation by introducing a new engine.