[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> But if we wanted to circumvent the upstream, I suppose someone could
> write a script which would go around every .js file in /assets/webpack
> and made sure the appropriate comment is added there.
That is not feasible.
1. Understanding the licensing of a file of code, with license notices
meant for humans to understand, and figuring out the proper equivalemt
machie-understandable notices meant to be read by LibreJS, requires
human intelligence. A "script" can't do it.
That is why we needed a different representation for LibreJS to use:
so it would not require human intelligence.
2. If anything causes use of JavaScript code from other sites,
we won't be able to add any comments to them.
In addition, this presupposes that the page in question is on a site
where we could modify it.
That might be the case. But we must not forget that requirement.