@@ -45,18 +45,19 @@ already there. Then, also check it meets the requirements below.
## What are the requirements an app must meet to be included with the repo?
The app …
*should be free (as in „free beer“ **and** as in „free speech“) and Open Source (see e.g. [Four Freedoms](https://en.wikipedia.org/wiki/The_Free_Software_Definition#The_Four_Essential_Freedoms_of_Free_Software) for what this means)
*must be free (as in „free beer“ **and** as in „free speech“) and Open Source (see e.g. [Four Freedoms](https://en.wikipedia.org/wiki/The_Free_Software_Definition#The_Four_Essential_Freedoms_of_Free_Software) for what this means). This includes using a libre license, approved by OSI/FSF (see [SPDX](https://spdx.org/licenses/)).
* must be targeted at end users (so no libraries, proof-of-concept demos, etc.)
* its code must be freely accessible, preferably at [Github], [GitLab], [NotABug], [Codeberg] or a similar platform
* if the app processes sensitive data (e.g. health data, passwords), is intended to improve security/privacy, has root permissions, or is targeted at children, it must have no trackers at all
* it preferably has no proprietary components. While some of them might be acceptable, trackers (e.g. ads, analytics) are tolerated at best but only if there are no more than two such modules.
* if the app processes sensitive data (e.g. health data, passwords), is intended to improve security/privacy, has root permissions, or is targeted at children, it must have **no trackers at all**.
* it preferably has no proprietary components. While some of them might be tolerable, trackers (e.g. ads, analytics) are bearable at best but only if there are no more than two such modules.
* it must not download additional executable binary files (e.g. addons, auto-updates, etc.) without explicit user consent. Consent means it needs to be opt-in (it must not be harder to decline than to accept or presented in a way users are likely to press accept without reading) and structured in a way that clearly explains to users that they’re choosing to bypass the checks performed in this repo if they activate it.
* that code repository should have a proper description so it gets clear what it is (if it's not, you must provide these details)
* the `.apk` file must be available from the project. Currently, *IzzyOnDroid* can work with files
* attached to GitLab `tags/`
* attached to Github `releases/`
* attached to Gitea `releases/` (e.g. at [Codeberg])
* uploaded inside a Github/GitLab repository as „part of the code“
* fixed URLs (like `https://example.com/app-latest.apk`) which can be redirects, but the web server must provide a `Last Modified` header
* attached to GitLab `tags/`
* attached to Github `releases/`
* attached to Gitea/Forgeio`releases/` (e.g. at [Codeberg])
* uploaded inside a Github/GitLab repository as „part of the code“
* fixed URLs (like `https://example.com/app-latest.apk`) which can be redirects, but the web server must provide a `Last Modified` header
Running on private resources (no funding), *IzzyOnDroid* usually reserves up
to 30 megabytes per app (exceptions are being made for larger apps, so this is
