You must log in or # to comment.
Eh, I don’t like better support for 3rd party repos. I’d rather devs meet the criteria to put their apps in the main repo.
The standards are high for a reason.
How does enabling third-party repo use prevent one from using the F-Droid repo?
I’d say continued improvement of third-party support suggests the main repo could be losing its value to users. There are apps in there over a decade old without even an anti-feature warning.
The effect is on the devs, not the users. If its lower friction for a dev’s users to install their app from their own third party app, then the devs are less likely to strip out anti features like reliance on third party trackers because they don’t have to do that if they host their own repo
I agree that what you’ve said is correct, but I don’t see how it would impede someone using the official repos. If telemetry is of major concern, there are alternative approaches (e.g. PiHole).
deleted by creator
clone comment
I don’t see how the ability of users to actually know which repository an app comes from and change the repository makes it more likely for devs to not remove anti-features.
I’ve had this exact issue a month ago where an app was available in official F-Droid repos and Izzy’s and I didn’t know which repo F-Droid selected by default.
Lowering the barrier of entry for dangerous options is an important UX decision.
Its the same reason it requires so many clicks to bypass a cert issue in browsers.
Installing from third party repos is dangerous. It should be possible, but not easy
So don’t use them?
The problem is that an app might not available in both.
Still no export/import of repos?
Did you open an issue for this on GitLab?
Nice! Very useful changes
Their SSL cert expired, must be one of those days where the renewal job failed for no reason like mine sometimes do lol
