Do our Android recommendations have to be in the official F-Droid repository? #1201
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1201
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This concern was rised in #1132 where I commented:
This issue also affects #1187 (& #1200) which aren't in the official F-Droid repository, but has its own repository. I think we also list Bitwarden that is in the same situation.
See also: #338.
First of all, we would need to decide whether this only cover the official f-droid repo, or being installable from any fdroid all repo.
In any case though, while I would see being on fdroid is a big bonus, I would not make it a requirement, as it would have the potentional to exclude some really good apps just for not being on fdroid.
Judging by the three 👍 to the previous comment, I guess our policy which just needs committing, is:
@privacytoolsIO/editorial further thoughts?
F-Droid is a distribution mechanism.
Technically it isn't centralized. There are f-droid mirrors.
The advantage of being in the official F-droid repository is that it must be open source and able to be built from that source. In addition to that there is some tracking on anti-features, which may not be the case in a third party repository.
Then there is the reproducible builds initiative. It is more desirable for the software to be in F-Droid and reproducible than in a third party repository and not be reproducible. You can see the recent builds from their wiki.
Also note that with Google Play, Google can push updates to you, whenever they want. Could select targets get a certain update that nobody else gets? Sure, you've got a set of login credentials attached to that software distribution center.