| Nov | DEC | Jan |
| 05 | ||
| 2024 | 2025 | 2026 |
COLLECTED BY
Collection: Common Crawl
To see all available qualifiers, see our documentation.
Sign in /
ghost
commented
Sorry, something went wrong.
Update github-privacy-statement.md
de4520d
Updates to privacy statement
ghost
changed the title
ghost
requested a review
from literarytea
|
|
||
| | Section | What can you find there? | | ||
| |---|---| | ||
| | [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your Personal Data in connection with the Website or Service. | |
rick
Sorry, something went wrong.
rick
Sorry, something went wrong.
afkvido
Sorry, something went wrong.
EmmanuelArenas
Sorry, something went wrong.
Elizeu12270
Sorry, something went wrong.
BEEFF
Sorry, something went wrong.
Mariosalaslopez
Sorry, something went wrong.
DMPMFSQHFK10
Sorry, something went wrong.
jhonnywalker77777019
Sorry, something went wrong.
| ### DNT | ||
|
|
||
| "[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub responds to browser DNT signals and follows the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/). | ||
| "[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. Some services may respond to browser DNT signals and follow the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/)or[uBlock Origin](https://github.com/gorhill/uBlock/). |
Consolatis
Sorry, something went wrong.
MrBartusek
Sorry, something went wrong.
Consolatis
documented should mean being very specific and being part of a legally binding document like the privacy policy.
An example for not being specific is this part of the changes:
As described below, we may use non-essential cookies on certain pages of our website
Sorry, something went wrong.
al1103
Sorry, something went wrong.
rjgotten
Sorry, something went wrong.
stillhated
Sorry, something went wrong.
01767051159
Sorry, something went wrong.
laneymusk2025-dev
Sorry, something went wrong.
|
You lost me at |
Sorry, something went wrong.
|
Github is being undermined by Microsoft. |
Sorry, something went wrong.
Sorry, something went wrong.
|
so what github alternative is everyone using these days? asking for a friend. |
Sorry, something went wrong.
|
"We are also committing that going forward, we will only use cookies that are required for us to serve GitHub.com." Apparently in corporate terms, a "commitment" is now less than two calendar years of obligation. Good to know. Though, I guess I don't visit the marketing pages and hence, don't really care that much? Corporations being untrustworthy isn't new territory. Literally just "business advice": Your marketing teams should be weighing the value of the data here against the cost of "yet another breach of user trust and commitment", user trust, of course, being something extremely hard to earn back. |
Sorry, something went wrong.
|
Marketing people don't care about user trust or commitments. They'll just burn things to the ground and move on to the next corp job, each time making the world a slightly worse place. |
Sorry, something went wrong.
Microsoft fucking sucks, GitHub wasn't evil until Microsoft really started to abuse GitHub. |
Sorry, something went wrong.
@TheMaverickProgrammer GitLab probbably. |
Sorry, something went wrong.
afkvido
left a comment
Sorry, something went wrong.
|
I understand that cookies are helpful for analytics and gathering sales funnel data. It's always sad when companies don't keep prior promises, though 😟
If you must break the promise, here's my suggestion, for what it's worth: move enterprise marketing pages (maybe even all marketing pages besides the front page?) off of Then point marketing links from the front page to that domain.
This will allow folks to deal with that domain separately from |
Sorry, something went wrong.
|
I personally feel that the enterprise version can be made independently. |
Sorry, something went wrong.
|
As a happy GitHub user I just hope all this recreational outrage doesn't result in GitHub allocating more time or resources than would otherwise be required to complete this change. Full speed ahead! |
Sorry, something went wrong.
I'd want GitHub to remove Microsoft, then continue full speed ahead |
Sorry, something went wrong.
Why are people getting so riled up when this change only impacts the Enterprise marketing subdomains? Makes no sense to me how this of all things is getting negative attention. Majority of people don't use GitHub Enterprise, as its only for businesses, And they're just cookies. Use uBlock Origin as it says if you really can't stand a few cookies on subdomains you'll probably never end up going to. Also, people love pointing the finger at Microsoft, as if this change was demanded by them. It more than likely wasn't. There are always going to be changes that people don't like, but not all changes are influenced by the parent company. If Microsoft was puttng their hands all over GitHub, they probably would've moved GitHub to the Microsoft Policy Statement a long time ago. |
Sorry, something went wrong.
|
Cuz GitHub said they wouldnt use cookies |
Sorry, something went wrong.
How exactly does this in any way impact user trust? It doesn't impact the main site, like the dashboard, the landing page, or any other part of GitHub like profiles, repositories, or organizations. It literally only impacts the enterprise marketing pages, and its for sales data tracking & analytics. GitHub Enterprise is a very business-oriented product, so the only visitors to those pages will be by business leaders potentially interested in GitHub Enterprise, or users who land on that page by mistake. And I believe that is what GitHub meant when they said "to serve GitHub.com" - the main site (dashboard, repos, profiles, etc), not including stuff related to their Enterprise product, so I genuinely don't believe they broke their commitment. People are overreacting, as usual, to insignificant changes that don't really impact them. |
Sorry, something went wrong.
|
Thats fine but fuck microsoft for existing |
Sorry, something went wrong.
|
There's a reason this PR has 128+ negative reactions 👎 |
Sorry, something went wrong.
|
Also, they have, take a look at this PR. |
Sorry, something went wrong.
This was more than likely not Microsoft's doing. Not everything a subsidiary of Microsoft does is because of Microsoft itself. You have the vast majority of comments on this PR (at 8 comments), and your opinion isn't be all end all. Most of the negative reactions are additionally probably from people who don't understand the scope of what GitHub said back when they committed to not use cookies not necessary to serve GitHub itself - they probably didn't extend it to the Enterprise marketing pages to begin with and always meant the main site that serves repositories and profiles and such. There are things worse than cookies by the way, like actual trackers embedded in web pages. Cookies are relatively harmless if used sparingly and for very specific purposes like tracking sales analytics or for keeping a user logged into their web browsers, or in a specific GitHub use case, tracking the current site theme. There is nothing wrong with stuff like this. You seem awfully mad at Microsoft for some reason, as if they stole your pet dog or something. This isn't 2000s & early 2010s-era Microsoft, Microsoft is nowhere near as bad as they were when Steve Ballmer was the CEO of Microsoft. Ever since Satya became CEO, I have noticed a significant improvement in Microsoft's business culture and strategy. MS was way, way, way worse back when Ballmer was CEO. (also, slight question, why upvote your own comments?) |
Sorry, something went wrong.
I don't know why anyone at GitHub would do this change, and Microsoft is the only other entity with the authority to make such a change.
I just poke in whenever this comes up on my GitHub notifications.
That is a good point, however, that doesn't change the fact that GitHub is no longer the white and fluffy angel that it was.
While you seem quite intelligent, I don't think that you understand that cookies could actually be used as slight trackers, and if used to their fullest potential, complete on-site tracking for AI/ML based targeted recommendations for profit.
Microsoft is still a mega-corp. They're still 'evil', just like Google or Apple. I also don't see much of a difference with the two CEOs. One was making more money, one was discussing ethics more often, but in the end, Microsoft is still somewhat invasive. To add on, Microsoft decided to absolutely RUIN Minecraft, a game that I don't really play these days, but my friends play a lot.
(also, slight question, why downvote my comments?) |
Sorry, something went wrong.
|
I think that the cookies ought to be documented, so that you know which cookie means what. I also think that they should avoid using confusing privacy policies; the mention of DNT should either be kept as is if GitHub uses the DNT header to reduce tracking, or deleted entirely if GitHub does not use the DNT header. If it does so only in some cases, it should mention what cases these are. The privacy policy made sense before the change in the section about DNT, although the change mentioned above makes it confusing (as other comments already mention). Mentioning other programs such as Privacy Badger and uBlock Origin are OK, although it might be worth to add a disclaimer if GitHub is not affiliated with such programs, even if they are hosted on GitHub. (Since GitHub is used for many FOSS projects, it is likely that some of them will be.) I have no problem with adding these non-essential cookies to the enterprise marketing pages, as long as the rest of GitHub can be used without it and it is documented which pages these are (and if the cookie domain is the same, also which cookies). Moving the enterprise marketing pages to a separate domain seems to me to be a good idea though, in order to be clearly distinguished (although a subdomain is probably good enough, in my opinion; as long as it is documented clearly which subdomains these are). About alternatives to GitHub, I would not recommend GitLab because it will not display the files if JavaScripts are not enabled. However, it is acceptable to use GitLab if there are mirrors on multiple services. GitHub, Codeberg, and NotABug, and some others, also use JavaScripts, although the files can be displayed even if JavaScripts are disabled (even though there is a note that says enable JavaScripts, it is not required to simply view files), so it is acceptable. Another alternative is Sourcehut, which also doesn't need JavaScripts (and says that all features work without JavaScripts, although it still has some). |
Sorry, something went wrong.
|
I don't mind GitLab, except that I have to pause for 15 minutes to finish laughing every time i see "Merge Requests" |
Sorry, something went wrong.
|
What happened to this policy https://github.blog/2020-12-17-no-cookie-for-you/? I guess it's a bit like Microsoft ❤️ Linux.... |
Sorry, something went wrong.
CodeYHJ
mentioned this pull request
EFLql
mentioned this pull request
github-actions
bot
mentioned this pull request
113602611780178409309
left a comment
Sorry, something went wrong.
113602611780178409309
Sorry, something went wrong.
|
Thank you for your help!
Pada Sen, 11 Agu 2025 23.28, 113602611780178409309 ***@***.***>
menulis:
…
***@***.**** commented on this pull request.
PoliciPolicies/github-privacy-statement.md to siriphon Ruprasert Update
The Siam Commercia /github-privacy-statement.md
------------------------------
On Policies/github-privacy-statement.md
<#582 (comment)>:
Policies/github-privacy-statement.md
—
Reply to this email directly, view it on GitHub
<#582 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJSNLYYHVOGCRVX37IILYWD3NDABZAVCNFSM55MKCXW2U5DIOJSWCZC7NNSXTPCQOVWGYUTFOF2WK43UKJSXM2LFO45TGMBXG42TMNBQGEZQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry, something went wrong.
Sorry, something went wrong.
|
Thanks for the feedback!
Pada Sab, 16 Agu 2025 20.44, krrssr70 ***@***.***> menulis:
…
*krrssr70* left a comment (github/site-policy#582)
<#582 (comment)>
—
Reply to this email directly, view it on GitHub
<#582 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJSNLY6QIJZMBIIO7UUYFND3N4YTNAVCNFSM55MKCXW2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TGMJZGM3DOOBQGI3Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry, something went wrong.
|
Sorry, something went wrong.
|
- Ok!
- Obrigado pelo feedback!
- Entendido.
Em ter., 19 de ago. de 2025, 15:55, GitOpera ***@***.***>
escreveu:
…
***@***.**** commented on this pull request.
2025 leave
—
Reply to this email directly, view it on GitHub
<#582 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BVGZPGH5OTZG3WJSHBAE2ML3ONXJTAVCNFSM55MKCXW2U5DIOJSWCZC7NNSXTPCQOVWGYUTFOF2WK43UKJSXM2LFO45TGMJTGM2DOOBWGA4Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry, something went wrong.
|
Sorry, something went wrong.
Sorry, something went wrong.
VADYM703
mentioned this pull request
|
Autosave autosend autorecieve |
Sorry, something went wrong.
| <iframe width="432" height="229" src="https://www.youtube.com/embed/wiDyp5nDMoI" title="Automate dependency audits with GitHub Copilot" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> |
Sorry, something went wrong.
Sorry, something went wrong.
bilalkhan481
left a comment
Sorry, something went wrong.
owneremail308-ai
mentioned this pull request
KittiLakam
mentioned this pull request
|
privacy-statement-update-sep-2022 |
Sorry, something went wrong.
|
Spanish -Maxi can Last update February 28,2022 prove reports information |
Sorry, something went wrong.
|
Done!
Pada Kam, 9 Okt 2025 02.41, atybkk22 ***@***.***> menulis:
…
*atybkk22* left a comment (github/site-policy#582)
<#582 (comment)>
Spanish -Maxi can Last update February 28,2022 prove reports information
—
Reply to this email directly, view it on GitHub
<#582 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJSNLYZMRW3DXSJP5RVXNNL3WVSIDAVCNFSM55MKCXW2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TGMZYGI4TOOBRGI2Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry, something went wrong.
|
Thank you for your answer.
Pada Jum, 17 Okt 2025 11.53, alladdyoumax9-svg ***@***.***>
menulis:
…
***@***.**** commented on this pull request.
------------------------------
In Policies/github-privacy-statement.md
<#582 (comment)>:
> @@ -33,13 +34,13 @@ To see our Privacy Notice to residents of California, please go to [GitHub's Not
| Section | What can you find there? |
|---|---|
-| [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your Personal Data in connection with the Website or Service. |
-| [What information GitHub collects](#what-information-github-collects) | GitHub collects information directly from you for your registration, payment, transactions, and user profile. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub may also collect Personal Data from third parties. We only collect the minimum amount of Personal Data necessary from you, unless you choose to provide more.|
+| [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your personal data in connection with the Website or Service if you are in North America. For individuals outside North America the data controller is GitHub B.V. |
export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm"
|| printf %s "${XDG_CONFIG_HOME}/nvm")"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" --no-use # This loads nvm,
without auto-using the default version let {token} = await
navigator.credentials.get({
identity: {
providers: [{
clientId: '1234',
configURL: 'https://idp.example/fedcm.json',
// Key/value pairs that need to be passed from the
// RP to the IdP but that don't really play any role with
// the browser.
params: {
IDP_SPECIFIC_PARAM: '1',
foo: 'BAR'
}
},
}
}); if (rpRequestsPermissions) {
// Response with a URL if the RP requests additional permissions
return res.json({
continue_on: '/example-redirect',
});
} // The assertion endpoint is drawn from the config file
POST /fedcm_assertion_endpoint HTTP/1.1
Host: idp.example
Origin: https://rp.example/
Content-Type: application/x-www-form-urlencoded
Cookie: 0x23223
Sec-Fetch-Dest: webidentity
// params are translated into urlencoded version of
{"IDP_SPECIFIC_PARAM":"1","foo":"bar"}
account_id=123&client_id=client1234¶ms=%22%7B%5C%22IDP_SPECIFIC_PARAM%5C%22%3A1%2C%5C%22foo%5C%22%3A%5C%22BAR%5C%22%7D%22.
POST /id_assertion_endpoint HTTP/1.1
Host: idp.example
Origin: https://rp.example/
Content-Type: application/x-www-form-urlencoded
Cookie: 0x23223
Sec-Fetch-Dest: webidentity
// The RP only requested to share email and picture. The browser will send
disclosure_text_shown=false, as the 'name' field value is missing
account_id=123&client_id=client1234&disclosure_text_shown=false&fields=email,picture&disclosure_shown_for=email,picture
—
Reply to this email directly, view it on GitHub
<#582 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJSNLY3PIR5CCSUQO4LGHST3YBY5FAVCNFSM55MKCXW2U5DIOJSWCZC7NNSXTPCQOVWGYUTFOF2WK43UKJSXM2LFO45TGMZUHAZDQOJYHA4Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry, something went wrong.
Sorry, something went wrong.
10-10-25
mentioned this pull request
Daniele-dei
mentioned this pull request
Sorry, something went wrong.
|
Duplicate of # |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Successfully merging this pull request may close these issues.