Comment by pastage 5 months ago So no F-Droid? 3 comments pastage Reply sdex 5 months ago Fdroid signs builds with own key, so it shouldn't be a problem if they pass this verification. mzajc 5 months ago As far as I understand, verification is tied to the package name (or at least the prefix). Since F-Droid packages thousands of applications from different developers, I don't see how they could reasonably get verified. BrenBarn 5 months ago It won't be a problem. . . until Google revokes their accreditation for some reason they won't explain.
sdex 5 months ago Fdroid signs builds with own key, so it shouldn't be a problem if they pass this verification. mzajc 5 months ago As far as I understand, verification is tied to the package name (or at least the prefix). Since F-Droid packages thousands of applications from different developers, I don't see how they could reasonably get verified. BrenBarn 5 months ago It won't be a problem. . . until Google revokes their accreditation for some reason they won't explain.
mzajc 5 months ago As far as I understand, verification is tied to the package name (or at least the prefix). Since F-Droid packages thousands of applications from different developers, I don't see how they could reasonably get verified.
BrenBarn 5 months ago It won't be a problem. . . until Google revokes their accreditation for some reason they won't explain.
Fdroid signs builds with own key, so it shouldn't be a problem if they pass this verification.
As far as I understand, verification is tied to the package name (or at least the prefix). Since F-Droid packages thousands of applications from different developers, I don't see how they could reasonably get verified.
It won't be a problem. . . until Google revokes their accreditation for some reason they won't explain.