Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

If you don't opt out by Apr 24 GitHub will train on your private repos

news.ycombinator.com

Post reply on HN
Print view View original

91–100 of 346 posts

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#91

Post by hirako2000 »

worble wrote: post #69
cj wrote: post #17

Earlier quoted context omitted.

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)

Pro tip: You could instead spend that money to spin up a forgejo instance for as little as $2 a month https://www.pikapods.com/apps#development (not affiliated, just a happy customer) Please don't reward these companies with money.

I did exactly that. Containerized it and Forgejo simply became a small instance part of the fleet. UI is much snappier then GitHub. And more importantly: zero outages.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#92

Post by moralestapia »

kepano wrote: post #12

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

Thank you for your service. We really need more "canaries in the mine" giving out early warnings of things that might not be evident on a first glance.

Any takes on what 2029 will look like? (related to this topic, ofc)

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#95

Post by miohtama »

mememememememo wrote: post #52
kepano wrote: post #12

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

Yes I think you are right. Even a super ethical company can be taken over. There may be exceptions but it is more luck. I work for a SP500 that absolutely won't dont this and locks down prod access so a rogue staff can't do it. But if Larry or Zuck or Bezos buys them out, who knows.

Microsoft would never do this

(-:

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#96

Post by tptacek »

jffry wrote: post #67
martinwoodward wrote: post #43

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.…

It's unnecessarily splitting hairs. > 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.

No it isn't. Most people don't use Copilot, so this term change won't effect most people. You can reasonably be unhappy about it anyways (or unreasonably still be using Copilot in 2026), but it's still ultra-useful information for them to add to the discussion.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#97

Post by layer8 »

martinwoodward wrote: post #43

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.…

In the EU, opt-out is not a legally valid way to obtain the necessary consent. How do you plan to handle this?

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#98

Post by daveguy »

martinwoodward wrote: post #43

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.…

Nice try. If you're training on "inputs" to Copilot then you are training on the private repos.

This suspect denial is why I will get my clients moved off of github.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#99

Post by ethanwillis »

martinwoodward wrote: post #43

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.…

"hope that helps"

Why the smug sarcastic attitude? nah, fuck github i'm out.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#100

Post by bsza »

I've been encrypting my private git repos for a while because I had suspected they were going to do something like this.

https://github.com/flolu/git-gcrypt

It's very easy to set up and integrates nicely into git. Obviously only works if you don't need Actions or anything that requires Github to know what's in your repo (duh).

Post reply on HN