If an app doesn't support reproducible builds, the version you can download from F-Droid was built and signed by F-Droid, not by the dev
kosmoz
joined 1 year ago
[…], from that point the app will be built by f-droid with their own digital signature.
This part of your comment is not quite true. One of the advantages of reproducible builds is that the app can be signed by the developer but fdroid can still verify that it has been built from the correct source code. You can check out the documentation here: https://f-droid.org/docs/Reproducible_Builds/
Cool but seems very unrelated?
I dislike Google as much as the next guy, but this seems to be an issue with the manufacturer (onn), not Google
Wouldn't that hurt Russia as much as any other country?
Happy Fairphone 4 user here! 🙂
Though I've heared mixed things about the FP5...
linked to Chinese speaking groups
What is that even supposed to mean?
Isn't one hurdle to integrate gtfs data into osm based apps the fact that there is no reliable way to link osm nodes with gtfs nodes? How did they get around that?
Does this mean that access to real time arrival data is on the horizon for osm based apps?
Edit: It appears that a lot has happened since I last checked, how cool!
Reference: https://wiki.openstreetmap.org/wiki/GTFS
Space cadet has been reverse engineered and can be installed in Linux through flatpak: https://flathub.org/apps/com.github.k4zmu2a.spacecadetpinball
I use ntfy and have no problems. It's very reliable. No idea about graphene though
Kagi supports this since a while. You can end your query with a question mark to request a "quick answer" generated using an llm, complete with sources and citations. It's surprisingly accurate and useful!
view more: next ›
There has actually been some progress on integrating GTFS data into OSM: https://wiki.openstreetmap.org/wiki/GTFS
I haven't yet seen much use of it in the wild though…