Still seeing posts from Lemmy about how @fdroidorg doesn't have in sync.
Still seeing posts from Lemmy about how @fdroidorg doesn't have @newpipe in sync.
They have an official repo. That will fix the problem.
NeoStore comes with NewPipe repo enabled by default.
https://github.com/NeoApplications/Neo-Store
@drakenblackknight @fdroidorg @newpipe
Even the official repository seems to update a day or so late. Most of the time the in-app updater notifies me about a new version, then I go check fdroid and the update is not yet available there.
They have an official repo. That will fix the problem.
Correct me if this is wrong, but from my understanding switching to their repo means no longer being behind F-Droid's source code match guarantee, or seeing anti-features and all that stuff. Granted, I already gave that up for Bitwarden so I admit it's a bit hypocritical, but much of the value of a centralized F-Droid is the main repo's curation process - circumventing it is a workaround, not a solution.
Edit: I also worry about the possibility - however remote - of downloading new apps thinking they're from the F-Droid repository, when they are in fact from some alternate repository I'm using. I already worry about this with Bitwarden, and each repo I add is another potential vector for this. Perhaps I'm overthinking this, but I'm thinking if too many popular apps make their own F-Droid repos, this might become a real threat.
@NeatNit
The other problem is trusting a centralized service implicitly. That's how people keep getting their login information exposed from Fakebook.
