transit systems that refuse cash payment and require an app for payment are a tax on the poor (as well as an imposition on everyone's privacy) and should be illegal
Realizing the irony that `git-annex sync` only supports commit message via -m (but it's targeting people who mostly don't care about commit messages and makes one up when not provided)
recently read a blog post that was arguing against using git commit -m and suggested that it might be worth learning the basics of nano or something in order to edit the commit message that way
Kind of flabbergasting, but is there a culture of only using -m in that is resulting in entirely oneline commit messages? See also commit messages that look like "feat: adding new feature to optimize apps" and "chore: add CI"
By facilitating a corporation that is attempting to set itself up as a governance over my community, how is Software Heritage not behaving in a way that runs counter to their mission statement of preserving software?
My immediate reaction is to consider removing my software from Software Heritage itself!
Asking to be removed from The Stack would implicitly legitimize this claim of governance over me.
(I should note that I've had considerable difficulty getting my software into Software Heritage in the first place, since I refuse to host it on Github. The irony.)
But they say nothing about stopping using models already trained on that data.
And "the most recent usable version" gives considerable leeway. Presumably if we all removed all our software from The Stack, it would no longer be usable.
Also, interesting how THEIR terms matter, but MY terms don't
The insufficiency is simple: When a LLM trained on software can output portions of copyrighted software, which they absolutely can and do, and when that gets used in proprietary software, all the provinance tracking of the dataset used to train it becomes irrelevant. At that point my license has been violated.
Software Heratige's statement's silence on this topic, in their list of principles, is deafening.
These seem like good principles. But they are not actually sufficient to respect our work. And the third is too weak, and appears to be providing a figleaf for extractive behavior.
"3. Mechanisms should be established, where possible, for authors to exclude their archived code from the training inputs before model training begins. "