Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutmIt wants me to uninstall and reinstall since the signature of different, which makes sense as it from a different source, but it doesn't mention anything in the changelog.
Jerboa is provided by both repositories. Izzy's pushed the update before F-Droid's is all. You can switch to Izzy's or wait or DL the apk from GitHub but signatures are different for all three.
Doesn't Izzy typically pull release directly from GitHub?
It does indeed
Do you know why the signatures would be different? At my company we release our app on Google play, galaxy and Amazon store and I'm pretty sure we use the same signing key for each
because fdroid build all of their apps themselves, so every app on the fdroid repo uses the fdroid signing key
Interesting, I was not aware of that. sounds like a security risk, as you don't know who actually published it, but I guess since its open source that doesn't really matter as much
You know who published it. It's the fdroid devs. Fdroid follows very much the old Linux repository philophosy where the owner of the repo acts as a middleman, providing the central layer of trust. You don't have to trust the developers because the distributor has done their due diligence and checked it. That's why fdroid takes a couple of days to push updates. They are doing some basic quality control first.
This model made a lot of sense in the world of traditional Linux packaging, where every obscure distribution has their own package format and developers couldn't possibly be expected to support all of these. It makes less sense on Android (or in a word where flatpak exists for that matter).
It makes less sense on Android
Quite the opposite. From the user perspective, it's much easier to trust the repository than trusting every single developer not losing their password. In case of OSS it also ensures reproducible builds.
It's actually the opposite, an evil developer could upload in GitHub an apk with malware not included in the source, while fdroid guarantees that it matches with the source published
I'd recommend giving this article a read, just to inform you about f-droid client https://privsec.dev/posts/android/f-droid-security-issues/
An alternative client being Neo Store
Privsec.dev is a libel slinger and an anonymity abuser on Reddit who is also Daniel Micay's equivalent of left hand. He is supportive of GrapheneOS and Micay's actions, and only went silent after Louis Rossmann exposed Micay.
Privsec_Dev/Tommy_Tran/B0risGrishenk0 did this to me last year. https://old.reddit.com/r/privatelife/comments/s0h73l/rprivacyguides_continues_its_harassment_campaign/
GrapheneOS members, Micay and his friends like Wonderfall have attacked F-Droid in the name of security, only to push using Google Play Store that annihilates all privacy of people. Google Play Services gather every possible metric about your phone which includes sensor, location, IP address, telephone number, IMEI and so on every 7 minutes. Just to be fair, Apple does the same things and is far worse. This theme of evangelising Google products at the cost of bashing all other projects is a thumb rule for GrapheneOS community.
https://forum.f-droid.org/t/what-are-the-issues-fdroid-have-about-security/17520
They didn't change the repo, it's just on both and f-droid repo updates slower.
It didn't change the repo. F-droid has always slower updates, because they're compiling every app themselves. Izzy is release directly from app developer, so it's newer. I'd stick to F-droid, so app dev can't push anything malicious in the official app build.
Izzyondroid gets updates faster. Give it a few days and the fdroid repo will get it
So that is what was going on. I was wondering why the update wasn't working.
What application is that? Some third-party app for GitHub?
Looks like Droid-ify, a third-party client for F-Droid.