4 ms·
Melodramatic. > I now have every incentive to not share my work, while also being wary of anything I find online that has been shared. If it hasn’t been pollut
by post-it 8d ago
Melodramatic.
> I now have every incentive to not share my work, while also being wary of anything I find online that has been shared. If it hasn’t been polluted by slop code, it might have been poisoned with a malicious library, send data off to third parties, or itself be comprised of someone else’s stolen work, implicating me in the crime.
All of this was a concern before.
> If I make my code available, AI can be used to more easily discover vulnerabilities to abuse my coding errors, while if I keep my code closed it is far more difficult to find those same mistakes.
This has always been a tradeoff.
> If I publish my code on a public service like GitHub, I am likely to be inundated with pull requests generated by AI bots and inexperienced users, flooding me with mostly useless slop and taking all of my spare time away just triaging it.
Then disable PRs?
This guy has four public repos on GitHub, two of which are forks. I get the impression he does more philosophizing about writing code than actually writing code.
- TeMPOraL 8d agoYeah, it just reads like inventing reasons not to contribute. If you don't want to contribute, then don't. There's no obligation to. That's a honest choice. LLMs don't affect those who want to gift contributions to humanity. On the contrary - they supercharge that gift. The only affected people are those who sold things, which is indeed unfortunate and I have lots of sympathy for - except for the subset of people who sold things while claiming they're altruistically contributing. LLMs ended up shining light at OSS/creative commons communities and revealed who there was giving things out, and who was secretly just selling stuff and using community goodwill for unfair advantage.