3 ms·
> In order to service the needs of GitLab.com and GitLab Self-Managed users who do not want to be tracked, both GitLab.com and GitLab Self-Managed will honor th
by oedmarap 7y ago
> In order to service the needs of GitLab.com and GitLab Self-Managed users who do not want to be tracked, both GitLab.com and GitLab Self-Managed will honor the Do Not Track (DNT) mechanism in web browsers. This means that, if you turn on Do Not Track in your browser, GitLab will not load the JavaScript snippet.
Ok so GitLab dotcom promises to honor DNT, which is good.
> GitLab Community Edition will continue to be free software with no changes.
So GitLab CE is not "affected" at all, which is better.
I've never used the Enterprise Editions, but what's to stop enterprise ops/sysadmins from just blocking the third-party requests at the DNS level (regardless of the DNT promise)? Another HNer mentioned this re: air-gapped deployments.
So in a purely practical sense, is the only noteworthy takeaway simply an extra production config step involving DNS?