I use F-Droid precisely because I don't want that. When <a href="https://news.ycombinator.com/item?id=38505229">https://news.ycombinator.com/item?id=38505229 happened - and when the same thing happens again in the future, because it will - I explicitly want F-Droid doing some basic due diligence on updates before shipping them to me. Cutting out the middleman is the opposite of what I want.
Counterpoint: I use NewPipe pretty much daily for watching YouTube. One day, YT introduced an API change that broke NewPipe, and so I patiently waited for an update.
A few days passed, and I eventually get a notification from NewPipe prompting for an update. But I can't install it just yet, because of mismatching signatures between the F-Droid and GitHub versions (yes, that's the point, I know...). The F-Droid build took so long to release, that in the meantime, another version of NewPipe came out...
True. And especially for that use, I can imagine that the slow return around is actually a breaking problem. I think there are relatively few apps that need that kind of quick update, and I'm more concerned with malicious authors than that, but it would depend on precisely what you need out of your apps.
aorth · · focus · HN ↗
yjftsjthsd-h · · focus · HN ↗
greeniskool · · focus · HN ↗
A few days passed, and I eventually get a notification from NewPipe prompting for an update. But I can't install it just yet, because of mismatching signatures between the F-Droid and GitHub versions (yes, that's the point, I know...). The F-Droid build took so long to release, that in the meantime, another version of NewPipe came out...
yjftsjthsd-h · · focus · HN ↗