From 2015 to 2022, I spent hundreds of hours on Duolingo, translating articles, answering language questions on the forums, and helping to improve the smaller courses by reporting mistakes.
There are thousands of volunteers who donated their labour to Duo: the course creators who wrote their courses, the volunteers who created grammar guides (some smaller languages had an entire second course in the forums), the wiki contributors, the native speakers who answered questions in the sentence discussions.
All of their work made Duolingo the powerhouse it is today. Duo was built by a community who believed in its original mission: language learning should be free and accessible.
Bit by bit all of our work was hidden from us as Duolingo became a publicly-traded company. And now that work is being fed into their AI as training data.
Well, I've learned the true lesson of Duolingo: never give a corporation your labour for free. Don't ever trust them, no matter what they say. Eventually greed will consume any good intentions.
#duolingo #languagelearning #enshittification #capitalism
To be fair every FOSS license will prevent a company from having exclusive rights to use your work. Even if you get a bit lax and include MIT and BSD licenses as FOSS, a company still cannot take your work and stop other people from using it.
In the case of Duolingo, it’s pretty different because that volunteer labor output is gated in a proprietary walled garden.
Whereas contributing a patch to chromium for example will never gate that contribution, even if it makes it into chrome and produces millions of dollars of profit for google. You can always and forever freely access and use a version of chromium with your patch as long as there’s still a copy left to access.
To be fair every FOSS license will prevent a company from having exclusive rights to use your work
The trajectory for many Foss projects is to get the hardest part off the ground with mindshare and initial development. Then after all the hard work it becomes successful, the project is closed and all new features are added into the closed fork.
Technically you still have the original work but within a few years the project is dead except for your personal work because the main fork has a large corporation behind it continuing the development.
To be fair every FOSS license will prevent a company from having exclusive rights to use your work. Even if you get a bit lax and include MIT and BSD licenses as FOSS, a company still cannot take your work and stop other people from using it.
In the case of Duolingo, it’s pretty different because that volunteer labor output is gated in a proprietary walled garden.
Whereas contributing a patch to chromium for example will never gate that contribution, even if it makes it into chrome and produces millions of dollars of profit for google. You can always and forever freely access and use a version of chromium with your patch as long as there’s still a copy left to access.
The trajectory for many Foss projects is to get the hardest part off the ground with mindshare and initial development. Then after all the hard work it becomes successful, the project is closed and all new features are added into the closed fork.
Technically you still have the original work but within a few years the project is dead except for your personal work because the main fork has a large corporation behind it continuing the development.