Crumb
c/android · by BlastboomStrice@mander.xyz · 3d

AI policies in fdroid (doesn't have a policy) and izzyondroid (no llm code allowed)

https://mander.xyz/post/57784042

Fdroid

Fdroid doesnt seem to have any llm-related policy about that yet

Izzyondroid

Izzyondroid has an exclusion policy for lmm-slopped apps and they need to pass some checks first

Vibe-coded apps will be rejected.

Apps acting as front-end for LLMs as outlined in point 6 above, or integrate with such services, will be rejected.

Readme, Changelogs and similar documentation files are allowed to include LLM-generated texts, but the code itself should be free of it.

Using LLMs for research, brainstorming, inspiration, debugging, look-ups, and comparable „read-only“ tasks, is acceptable – provided their output is not included in the app's code.

4 points · 4 comments · view on lemmy.world

4 Comments

Zykino@programming.dev · 2 pts · 3d (1 reply)

Izzy allow non-open source apps. They say they will check, but how can they? Already with the source on hand it is not always easy to determine if the code is from am AI so on parts where sources are not available…

BlastboomStrice@mander.xyz · 1 pts · 3d

Hmm it seems like they approve proprietaey components under some exceptions, dunno how they could test for llm-slop. But either way, they tend to ask the developer for llm use disclosure, so a developer could lie and have their app passed (though if somehow it's proven they used llms in unwanted way, they'd have issue). Also I guess the developers woild have to justify a proprietary component and theyd have to hide that it's partial purpose is llm code. Shrug

https://izzyondroid.org/docs/general/AppInclusionPolicy/#code-and-license

  1. License: The app and its code must be free (as in „free beer“ and as in „free speech“) and Open Source (see e.g. Four Freedoms for what this means). This includes using a libre license, approved by OSI/FSF (see SPDX).
  1. The app's code must be freely accessible, preferably at Codeberg, GitLab, Github, or a similar platform (self-hosted Forgejo/Gitea/GitLab instances are supported as well, if they are „permanently“ online and openly accessible).
  1. there should be no proprietary components. While some of them might be tolerable if they are essential for the app's core functionality, trackers (e.g. ads, analytics) are not. In addition to them not being F/LOSS, such modules are considered as too intrusive, and hence rejected in general.
mike_wooskey@lemmy.thewooskeys.com · 1 pts · 3d (1 reply)

What definition of "vibe coded" are they using?

BlastboomStrice@mander.xyz · 3 pts · 3d

From what I understand from the rest, they (at least) dont want any llm output to be inside the code of the project