61–70 of 346 posts
You don't want an LLM trained on my private repos. Trust me.
How do I opt out of this for my own private repos? I don't see anything related to this as I've got a ton of settings for Copilot itself (I have access to Copilot through my work org)
Under privacy. > Allow GitHub to use my data for AI model training
No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
Jokes on them, my private repos are total dog dookie. If nobody but me can see the code then I don't have to worry about style, structure, comments, or any other best practices. You don't want an LLM trained on my private repos. Trust me.
I wonder how effective it would be to sabotage the training by publishing deliberately bad code. A FizzBuzz with O(n^2) complexity. A function named "quicksort" that actually implements bogosort. A "filter_xss" function that's a no-op or just does something else entirely. The possibilities are endless. I thought of this after remembering seeing a post a couple months ago about how it doesn't take a significant amount…
I'm absolutely sure that there are state actors with gigantic budgets that are putting a lot of effort into similar attacks, though.
No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
> interaction data—specifically inputs, outputs, code snippets, and associated context [...] will be used to train and improve our AI models
So using Copilot in a private repo, where lots of that repo will be used as context for Copilot, means GitHub will be using your private repo as training data when they were not before.
I've been saying this since 2023 > If your data is stored in a database that a company can freely read and access (i.e. not end-to-end encrypted), the company will eventually update their ToS so they can use your data for AI training — the incentives are too strong to resist https://news.ycombinator.com/item?id=37124188
Edit: Okay, sounds like you guys are pissed to the point where it seems like the pro tip here is to stop using GitHub. Pro tip: sign up for the business/enterprise version when reasonable in price. I do this with Google Workspace. You can also do it with GitHub. (Google doesn’t train on Workspace, Github doesn’t train on business customers, etc)
Please don't reward these companies with money.
No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
Honestly, if you work at GitHub, maybe you should focus on your uptime -- it's awful.