Okay, here is the abstract and summary for the provided transcript.
Abstract:
This document discusses the ban of the VLC for Unity integration from the Unity Asset Store in late 2023, as detailed in a blog post by Martin Finkel of VideoLAN. The author recounts Unity's reasoning—citing LGPL licensing concerns—and highlights the perceived hypocrisy, as Unity itself and many other store assets utilize LGPL dependencies. In response, VideoLabs (which employs core VLC developers) launched its own store to distribute VLC for Unity binaries and offer multimedia consulting services.
The accompanying Hacker News discussion delves deeply into the nuances of LGPL vs. GPL, the legality and practicality of Unity's stance, and the potential misinterpretations by Unity's legal team. Commenters debate the conditions of LGPL compliance (especially regarding static vs. dynamic linking and modification on locked-down platforms like consoles), Unity's inconsistent enforcement, and the company's history of controversial decisions. The relationship between VideoLabs and the VideoLAN non-profit is also clarified.
Unity's Ban of VLC for Unity: The Full Story and Community Reaction
Article: VLC for Unity Banned: In late summer 2023, Unity banned VideoLAN's VLC for Unity assets (Windows, UWP, Android integrations) from the Unity Store, citing issues with LGPL-licensed code. The publisher account was instantly banned with no recourse despite attempts to compromise.
Article: Unity's Perceived Hypocrisy: The author points out that hundreds of other Unity assets include LGPL dependencies (like FFmpeg) and that Unity's own Editor and runtime use LGPL libraries (e.g., Lame, libiconv). This suggests inconsistent or targeted enforcement.
Article: Videolabs Store Launched: Following the ban, VideoLabs (a company employing core VLC/FFmpeg developers) created its own online store to continue providing VLC for Unity binaries to existing and new customers.
Error: Couldn't find 2529 Users can still build the open-source VLC for Unity themselves.
Article: Consulting Services Offered: The Videolabs Store also offers flexible multimedia consulting packages for LibVLC and FFmpeg, providing expert help with custom builds, bug fixes, SDK integration, and more.
Article: Other Products: The store includes the LibVLCSharp commercial license, a LibVLC ebook, and will feature upcoming products like Kyber (an ultra-low latency streaming SDK) and integrations for other game engines like Unreal.
Hacker News (jdlyga): LGPL vs. GPL Distinction: A key discussion point is the difference between LGPL (allows linking with proprietary apps under certain conditions, like allowing library modification) and GPL (requires the entire derivative work to be GPL). Some speculate Unity's legal team confused the two or intended to only screen out GPL.
Hacker News (jmull, roblabla): LGPL on Signed Platforms: Debate arises whether distributing LGPL software on platforms requiring signed apps (like consoles) complies with the license, as users might not be able to modify and relink the LGPL components. It's noted that LGPLv2.1 (used by VLC) lacks the "anti-tivoization" clause of LGPLv3, potentially making it more compatible with such platforms.
Hacker News (ack_complete): Asset Store Specific Rules: It's argued that Unity can have stricter rules for its Asset Store than for the engine itself. The primary issue raised is the uneven enforcement of these rules against different assets.
Hacker News (phkahler, jcelerier, voxic11): Static vs. Dynamic Linking & LGPL: Discussion clarifies that while dynamic linking is a straightforward way to comply with LGPL, static linking is also permissible if the application is provided in an object format, allowing users to relink with a modified library.
Hacker News (NoahKAndrews, jbk, Ragnarork): VideoLabs and VideoLAN Affiliation: Initial confusion about the relationship between VideoLabs and VideoLAN was clarified. VideoLabs employs most of the core VLC developers and contributes significantly to VLC, a common model for sustaining open-source projects.
Hacker News (w4rh4wk5, tzs): LGPLv3 and Tivoization: Concerns about Unity's own dependencies (like websockify.js under LGPLv3) on locked-down platforms led to a detailed explanation of the *GPLv3 tivoization clause, suggesting it's narrowly defined and likely doesn't prevent distribution of add-on software on consoles, though app store TOS could still pose issues.
Hacker News (adzm, axus): Unity's Provider Agreement: It was noted that the clause restricting LGPL assets was seemingly removed from the main provider agreement but then located within the Asset Store's "Submission Guidelines."
Hacker News (General Sentiment): Frustration with Unity: Many commenters expressed frustration with Unity's decision, viewing it as poorly justified, hypocritical, or part of a pattern of anti-developer actions. The incident reinforced negative perceptions of Unity's management.
Hacker News (mouse_, diggan): Unity's Own LGPL Use: The irony of Unity banning LGPL assets while using LGPL components in its own products was a recurrent theme, labeled as a "double standard."