godiff

Because it can be fixed trivially, eliminating the threat? Literally, it already happened here: https://github.com/seletskiy/godiff/commit/865648740d705a24a... Just as described, the problem was raised and then fixed. Now let's assume someone like Oracle goes and acquires 1000 unlicensed tiny open source projects, just to be a dick, and closes their source and begins copyright trolling. Here's what happens: people switch off of those projects. I'm not trying to diminish the usefulness of godiff; it is useful! But it's not literally irreplaceable; there may even already be other options in the ecosystem, and if there's not, it's not something that can't be removed temporarily, and replaced long-term. This blog post is a little alarmist IMO, but people who do this kind of sleuthing are doing a service to the open source community, because y

The author of the Go diff library has just released it under the MIT license: https://github.com/seletskiy/godiff/commit/865648740d705a24a...

To add, as the article says, the GH issue[0] was posted on Dec 18, 2020 by Norwin @noerw who is a member of the Gitea GitHub organization[1], so Gitea is definitely well-intentioned on clarifying the license of code it uses. 0: https://github.com/seletskiy/godiff/issues/4 1: https://github.com/orgs/go-gitea/people?query=noerw