Maybe it is time for a #floss license that forbids automatic analysis of code.
Problematic for linting and similar tools, but I bet there's a way around that. Something like "if the data retrieved from an automatic analysis is stored, that's for bidden" or something like that.
@musicmatze Hmm, I think prohibiting certain use cases (like analysis) is hard to get right. I.e. I think something like this would often lead you to restrict things you actually want to allow or allow things you really want to restrict.
Maybe a copyright reform is needed that defines how the copyright of input data affects the copyright of machine-generated outputs? Though that also opens a whole other can of worms ...
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!