Has a bespoke "community" licence ever actually stopped somebody from shipping a repack?
热度趋势
趋势数据积累中
百分比基于当前可用热度信号，而非评论数或独立用户人数。
讨论围绕着定制的“社区”许可在阻止未经授权发布衍生作品或重新打包方面的有效性。核心问题是，这种许可是否曾成功阻止某人发布修改后的副本，因为许可只有在外部方试图这样做时才真正受到考验。一个被引用的例子是Ling 3.0 Flash，它对一个总计124B、活跃发布5.1B的项目使用了普通的MIT许可，但这个案例并未解决社区许可的效力问题。
A licence only gets tested when somebody outside the lab wants to publish a modified copy.
Everything before that is a download button. The screenshot is a build nobody at the lab made. A third party converted it and repacked it, it loads on someone else's machine, and the repack carries the same licence tag as the original. It's a load screen, nothing dramatic.
Ling 3.0 Flash is a dull case on this axis. Plain MIT on a 124B total, 5.1B active release.
Says nothing about whether the model is any good. So this is me asking for the other side of it. Has anyone got a case where a bespoke community licence actually stopped a derivative from shipping?