Voice.ai: GPL Violations with a Side of DRM (undeleted.ronsor.com)

Article summary

The article discusses how Voice.ai, a real-time AI voice changer software, violates the GPL and LGPL licenses by using and distributing code from Praat and libgcrypt without providing the required source code. The author discovered the violation by analyzing the software's files and contacted the developers, who have not responded. The software also collects user data and uses obfuscation techniques, raising concerns about its legitimacy. The developers have since released an updated version that removes the GPL-licensed code, but still violate the LGPL license.

Main themes

• GPL and LGPL license violations
• Software obfuscation and data collection
• Open-source licensing and enforcement
• Developer responsibility and accountability
• License compatibility and virality
• Community response and legal action

What commenters say

• The GPL license requires distributors to provide source code, and Voice.ai's failure to do so is a clear violation.
• The LGPL license allows for more flexibility, but still requires providing source code or a way to relink with the licensed library.
• Some argue that the GPL's viral nature is a misconception, and that it's up to the author to choose how to license their work.
• Others point out that even permissive licenses require attribution, which Voice.ai is also violating.
• The fact that Voice.ai is using obfuscation techniques and collecting user data raises concerns about their intentions and legitimacy.
• The company's response to the allegations, including banning the person who reported the issue, is seen as unprofessional and potentially illegal.
• It's suggested that the owners of the open-source projects should take legal action against Voice.ai to enforce their licenses.
• Some argue that the OSS community needs a legal team to represent license violations and defend open-source projects.