Wondering if we should modify statistics.js to only run the ajax command if counter if !navigator.doNotTrack && !navigator.msDoNotTrack. I'm not sure this is worth it considering that nothing personal is tracked in the node counter. And accesslog, which used to store things like IP address, has been removed from D8 core.

Resources

http://donottrack.us/
https://developer.mozilla.org/en-US/docs/DOM/navigator.doNotTrack
http://ie.microsoft.com/testdrive/browser/donottrack/default.html

Comments

mfb’s picture

IMO I don't think a site counting visits to its own pages, without any identifying information, would be considered tracking for purposes of Do Not Track. DNT is primarily concerned with third-party tracking by sites you did not explicitly visit, as per http://donottrack.us/ and https://www.eff.org/deeplinks/2011/02/what-does-track-do-not-track-mean

Note, at present drupal 8 is still logging IP address in the comment (if a comment is created), sessions (if a session is saved) and watchdog tables (if an error/warning/notice is logged).

iamEAP’s picture

Agreed, node counter is outside of the scope of the spirit of the DNT header. Propose we close this out as "won't fix."

mgifford’s picture

Title: Should the statistics node counter respect the Do Not Track setting? » What is the best practice for respecting a users Do Not Track setting?
Version: 8.x-dev » 9.x-dev

Good question though @Dave Reid. It would be good if there were a Drupal module that's out there that is already exploring this space.

With things like the EU Cookie laws, it's encouraging to see:
https://drupal.org/project/eu-cookie-compliance

But I do think that there is probably going to be increased awareness of privacy options and CMS's that are able to support that.

I'm going to bump this issue ahead to D9 rather than setting it as won't fix rather than setting it as won't fix. I think the focus should be on the Do Not Track setting rather than specifically on the counter "Should the statistics node counter", so changed the title.

Heck, if Twitter is supporting this.....

catch’s picture

Version: 9.x-dev » 8.1.x-dev
Issue summary: View changes
Status: Active » Postponed

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Wim Leers’s picture

Status: Postponed » Closed (works as designed)

This is definitely not "tracking", as others have already pointed out.