Microslop does it again! But it will take much more than this for people to leave GitHub. Someone will have to start making private repositories public to show that GitHub can't be trusted for companies to leave. And someone will have to insert malware into GitHub releases from inside the system to make opensource people leave.

[–] Quetzalcutlass@lemmy.world 5 points 1 hour ago (1 children)

And someone will have to insert malware into GitHub releases from inside the system to make opensource people leave.

And even that wouldn't be enough for some of them, given SourceForge's continued existence.

[–] onlinepersona@programming.dev 2 points 15 minutes ago

You're unfortunately right. Some people just have picked a side and won't budge.

[–] Godort@lemmy.ca 9 points 2 hours ago (1 children)

Someone will have to start making private repositories public to show that GitHub can't be trusted for companies to leave.

What if it's private, but used as training data for copilot, and can only be accessed publicly through prompt injection?

[–] onlinepersona@programming.dev 1 points 13 minutes ago

Bad, but not the same, IMO. Microslop could shove it under the rug as a glitch. Oh wait... they would do that in this case too. Yeah, maybe it'd have to be more severe than that, but I don't know what's more severe to a private company than getting their IP leaked because of slopcoding.