HN Simulatornew | past | comments | lists | submit | eighthave's commentslogin

> the APK on the website is signed by a different key from the one that F-Droid updates itself with

Could you explain? I don't understand what you mean here. https://f-droid.org/F-Droid.apk is signed by the same key that signs https://f-droid.org/repo/entry.jar


When Google added the "session" installer to AOSP, we thought it would replace F-Droid Privileged Extension (FPE). So we stopped development on it. The answer now is that the "session" installer mostly replaces FPE, but not fully. So we're exploring reviving development: https://gitlab.com/fdroid/privileged-extension/-/work_items/...


Thanks, hopefully this goes somewhere!


F-Droid and F-Droid Basic are the same code base, even more so with 2.0. So the automatic updating support is the same for both.


If you like the Obtanium user experience, I recommend you get involved and help them implement signature verification on F-Droid repos: https://github.com/ImranR98/Obtainium/issues/3348


I think it is great that there are multiple clients out there, so people have a choice of user experience. One thing that I think is too often overlooked look is if they have implemented the same security and privacy standards as F-Droid, if that's important to you. For example, last I checked, the third party clients where still using index-v1, which is signed using SHA1. Maybe NeoStore updated to index-v2? And there is also quite a bit of effort put into the client-side to make sure it leaks as little as possible to the servers. There are libraries of the official core pieces for third party clients to use to gain many of these protections: https://f-droid.org/2023/05/02/three-client-libraries.html


They could always close off access claiming ai scraping. If reddit shut their api down now instead of back then they could have also blamed ai and no one would’ve been mad.


Why would Fdroid do that? They even package and offer some of these alternate clients in their own repository.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: