Re:F-Droid and Google's Developer Registration Decree
by weikju on Tuesday September 30, 2025 @03:20AM
(#45422809)
That makes a lot of sense. Unfortunate indeed that Google would be the sole arbiter of that “DNS”, but that explanation was pretty good
Re:F-Droid and Google's Developer Registration Decree
by airhangerf15 on Friday October 03, 2025 @10:56PM
(#45470137)
F-droid only distributes apps it builds (unless you add an additional repository). The official F-droid repository only contains code they build from source. You can't upload binaries/bytecode to the official F-droid repo.
Re:F-Droid and Google's Developer Registration Decree
by fluidcruft on Saturday October 04, 2025 @10:35AM
(#45473613)
I am well aware of that? What does that change?
For example, there is an annoyance that happens sometimes with apps that are distributed in both F-Droid and Play Store related to updates. F-Droid and Play Store will think they both can update the app (they have the same tld.what.ever identifier) but the signing keys only match the store they were installed from. I think F-Droid is now a bit more careful about this and only tries ones it has specifically installed. This is different... but somewhat related.
F-Droid in general is a model good actor as far third-party app stores go, but from the perspective that malicious app stores might exist you would want to try and isolate apps from each other (and prevent unauthorized re-distribution of tampered versions etc). I think what Google is doing forces apps in each store to be cleanly namespaced from each other and prevent collisions (accidental or otherwise). This lets each app store tend and be responsible for its own walled garden.