@bekkaboo@girlcock.club Linux itself is heavily using AI models. Therefore, every Linux distribution moving to recent kernel versions is heavily built on top of using AI models. Creating a Linux distribution not heavily using it would require a hard fork of the Linux kernel and many other projects.
It's unclear what would be accomplished by banning AI for a tiny portion of the code while continuing to use Linux, AOSP, Chromium and hundreds of other projects heavily using it. We'd still be benefiting from it.
GrapheneOS is currently defending its use of AI coding tools on Mastodon against complaints by various accounts claiming to be users.
We do not understand where you’re coming from or why you’re so incredibly angry with us. It’s not justified and does not make sense.
Another thing is I think one can analyze binaries (decompiled or not) to extract control structures in machine code or byte code to control flow graphs. Using some classical pattern matching, that should not be too difficult because the number of ways compilers transform code like loops are limited. Allowing some degree of fuzziness, I’d often expect these to be very characteristic for the original source of a code piece. That source might often be FOSS code; often an old, vendored version not updated in years.
One could then use standard graph search/fuzzy matching algorithms and graph databases in order to find out which GPL’d open-source code e.g. some proprietary product has included. This would give away potentially vulnerable versions. And it would not necessarily need a lot of computing resources.
Another thing is I think one can analyze binaries (decompiled or not) to extract control structures in machine code or byte code to control flow graphs. Using some classical pattern matching, that should not be too difficult because the number of ways compilers transform code like loops are limited. Allowing some degree of fuzziness, I’d often expect these to be very characteristic for the original source of a code piece. That source might often be FOSS code; often an old, vendored version not updated in years.
One could then use standard graph search/fuzzy matching algorithms and graph databases in order to find out which GPL’d open-source code e.g. some proprietary product has included. This would give away potentially vulnerable versions. And it would not necessarily need a lot of computing resources.
I’m just waiting for Microsoft and Windows to get blown wide open by this Pandora’s box they’ve opened.