Live data from Hacker News

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

news.ycombinator.com

321–330 of 346 posts

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

#321
post #88

I'm looking forward to the class action lawsuit, even if only to establish a precedent! I don't have much hope, but I wish that ignoring software licensing and attribution at scale becomes harder than it currently seems.

They would've done the math. Even with a class action they will come up positive. It just another bill for them.

Would be good to actually make them pay that bill though.

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

#324

Earlier quoted context omitted.

I've never seen the banner. Where does this show up?

It's been on top of the web UI for 2 or 3 days now. You might have closed it... Just go to your account settings and find the opt-out option.

Honestly there go months between me visiting github.com, let alone as a signed in user.

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

#325

Earlier quoted context omitted.

Conceptually I think it’s a fine comparison. They’re training (with an opt out) on stuff people feel is an invasion of their privacy to make their service better.

> (with an opt out) And this is the problem: any time you're adding a new "feature" that invades users' privacy, it needs to be opt-in .

> it needs to be opt-in.

And again: Google did this and everyone eventually got over it. Cars do this with telematics data and everyone is over that too.

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

#326

Earlier quoted context omitted.

> (with an opt out) And this is the problem: any time you're adding a new "feature" that invades users' privacy, it needs to be opt-in .

> it needs to be opt-in. And again: Google did this and everyone eventually got over it. Cars do this with telematics data and everyone is over that too.

That doesn't change the ethics of it.

The only reason that worked is because Google is an unstoppable monopoly juggernaut whose name is literally synonymous with searching the web.

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

#327

Earlier quoted context omitted.

As opposed to other places where Microsoft is just shit? :)

It's my favorite slow burn, 'the shit' is a good thing, but everything is backwards in Soviet Russia...

That's what I understood, just wanted to make sure I wasn't reading too deeply into it :)

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

#328

Earlier quoted context omitted.

> https://github.blog/news-insights/company-news/updates-to-gi... > Should you decide to participate in this program, the interaction data we may collect and leverage includes: > - Outputs accepted or modified by you > - Inputs sent to GitHub Copilot, including code snippets shown to the model > - Code context surrounding your cursor position > - Comments and documentation you write > - File names, repository structu…

Do you use copilot?

Do you think a single person works on a repo?

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

#329

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

I'm in the process of moving all of my repos off of github and deleting that account.

Hope that helps.

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

#330
post #236

Earlier quoted context omitted.

The setting isn't even visible to everyone. If you're currently in an org that manages copilot business, it's gone. I imagine it instantly opts you back in when you leave an org.

My work was careful to explain: if you associate your personal GitHub account with their work org copilot, then they are the ones who manage copilot. If you wouldn't use your personal email account on your work computer, I don't see why you wouldn't create a new GitHub account only for work.

There have been instances where GitHub has banned users for using an email address from a custom domain. If your account is associated with an enterprise plan the chances of that happening decrease significantly. Also puts you in much better position for recourse
Post reply on HN