问HN：开源分叉是否能减轻作者的监管责任？
许多司法管辖区正在通过法律，要求软件实施合规机制：年龄验证、内容控制、用户监控。这些法律给开源作者带来了问题，因为他们无法控制自己的软件如何被分发或使用。
我一直在发展一个论点，即“分叉权”（开源许可证授予任何方修改和重新分发软件的不可撤销权利）从根本上改变了原作者的责任状况。
简要论点如下：
当一个司法管辖区强制要求合规机制时，它实际上是在强制修改软件行为。开源许可证已经赋予该司法管辖区进行这种修改并分发结果的法律权利。因此，合规路径是存在的，并且对任何愿意使用它的方都是可用的；包括监管的司法管辖区本身。
这意味着原作者并没有拒绝合规。他们在结构上使合规成为可能，但并不是实施合规的控制方或有义务方。负有义务的一方是对该司法管辖区内分发进行控制的方；这可能是该司法管辖区本身、当地分销商或应用商店。
如果这个论点成立，那么它对开源作者如何应对加州AB 1043、欧盟的DSA以及类似法律将产生重大影响。
我确实不确定这个论点是否以前以正式的方式提出过，以及它在合规或执法的背景下是否能够经得起审查。
有没有人曾在法律或政策背景下遇到过这个论点？它是否成立？
查看原文
A number of jurisdictions are passing laws requiring software to implement compliance mechanisms: age verification, content controls, user monitoring. These laws create a problem for open source authors who have no control over how their software is distributed or used.<p>I've been developing an argument that the right to fork (the irrevocable right granted by open source licenses to any party to modify and redistribute the software) fundamentally changes the liability picture for the original author.<p>The argument in brief:<p>When a jurisdiction mandates a compliance mechanism, it is mandating a modification to software behavior. Open source licenses already grant that jurisdiction the legal right to make exactly that modification and distribute the result. The compliance pathway therefore exists and is available to any party with the will to use it; including the regulating jurisdiction itself.<p>This means the original author has not withheld compliance. They have made compliance structurally possible while not being the party with either the control or the obligation to implement it. The party with the obligation is the one exercising control over distribution within the jurisdiction; which may be the jurisdiction itself, a local distributor, or an app store.<p>If this argument holds, it has significant implications for how open source authors should respond to regulations like California AB 1043, the EU's DSA, and similar laws.<p>I'm genuinely uncertain whether this argument has been made formally before, and whether it would survive scrutiny in a compliance or enforcement context.<p>Has anyone encountered this argument in a legal or policy context? Does it hold?