-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Privacy Issue with nodejs.org Tracking Statistics and Marketing Without User Consent #2302
Comments
@june07 it seems like all of the unnecessary cookies on the domain are coming from google analytics, which we had attempted to remove in 2018... it looks like we missed a couple references... I've opened a PR to fix that. If I'm reading the report correctly we should be compliant after that lands as we will only have the cloudflare cookie with is deemed "necessary" and allowed by GDPR without a notice. I understand you are upset with us, and genuinely appreciate a call to action for us to do better... but I have to honestly say that the way you are engaging, the extent of content, the way you are presenting it, makes it seem like you have a vendetta and are trying to prove a point. Seeing folks be hypocritical is frustrating, but if you continue to engage like this you are going to only distance yourself from the project and risk longer term repercussions in your ability to participate in our projects. This website is run by volunteers and I urge you to consider that. |
We removed GA in 2018 but it seems like we missed removing it from the partials and it is still being loaded. Refs: nodejs/node#23083 Refs: #2302
@june07 Does this issue still stand after #2305 being merged? Thanks for locating the Google Analytics traces, btw, that was apparently missed last year when it was removed. @MylesBorins Thanks for taking care of that! |
@MylesBorins "Disappointed" would be a more apt description of my current feelings. However I will also add that my engagement, content, and presentation has been far from brash. I'm simply presenting FACTS from a vantage point that seems to differ widely from many here, as well as a historical (very recent) view into the different manner we are treating/have treated issues/individuals/organizations. If my doing so results in "longer term repercussions" as you state, that would be unfortunate. As you so rightly put it,
I'm at least glad you, yourself, called attention to the hypocrisy above... and if me calling it or other issues out is a problem... well, that is a problem. FYI: Node is not unique in it's being run by volunteers, and my consideration of that is constant, yet it doesn't excuse the preferential treatment, bias, and hypocrisy I've been witness to. I'm glad this is being resolved. It's a perfect demonstration of how OSS should work. Problem identified, people work together, problem fixed. More emphasis should be put on fixing things and working together... regardless of the time/effort involved in doing so... and that ethos should extend to EVERYONE. And please, consider my continued attempt of amicability. |
It was still present in one file, previous commit just removed the prefetch. Also remove dnt_helper, it was used only by analytics. Refs: #2305 Refs: nodejs/node#23083 Refs: nodejs/node#22652 Refs: #2302
@fhemberger
Interesting how this has not been addressed, as it seems to clearly fit:
Link to the full report
Given your quickness to point to GDPR in the recent past, I assume you already know this information but here is the link anyway: https://ec.europa.eu/info/law/law-topic/data-protection_en
@ea167
@oncletom
@WaleedAshraf
@tniessen
Maybe we could all do well by looking into the mirror.
The text was updated successfully, but these errors were encountered: