• 6 Posts
  • 33 Comments
Joined 3 years ago
cake
Cake day: November 3rd, 2021

help-circle
  • F-Droid produces its own builds, with its own signatures, so to get f-droid going, you’ll need to install from F-Droid. However the import mechanism seems really nice. Perhaps you can install from F-Droid the official release, which can co-exist with your upstream installed beta release, import from it from the F-Droid app, then remove the upstream installed beta release, and if you wan to keep on beta, then install the beta release from F-DRoid (be careful right now, given a bug made K9 show up as beta release as well, but the app ID is clear, just being careful is enough), and then import from the official release, then remove the official release and you’re all set. The idea is not to reconfigure a thing by doing those steps, and perhaps you wouldn’t like to go to beta, and remain on the official release, which is not that behind, and perhaps better tested.


  • Did that, thunderbird release no beta, and no issues since I don’t have google account. For people with google account requiring to re-sign in, and who don’t often do so, signing in is really hard if they don’t registered their phone number to google. It’s sad, I commented about it in some other post. Understandable in reality they are different apps, but in the end it should be the same user ID, but nevertheless it’s a PITA if people don’t have a device permanently logged in, :( For them it’s better to stay on K9,and hope K9 doesn’t go away, or else find out how the heck to login to google once again.



  • Sadly, when having a gmail account, the migration is not possible, if the user doesn’t keep permanently logged in somewhere. TB is not taking the current K9 OATH, and tries to establish it’s own authentication, which on a K9 + desktop TB user not logging often to google at all, it’s really almost impossible to login to gmail, since it ask as security the user 1st phone number, which could have never been registered to google, and beyond that it requests to use a different device which is already logged in, but it you go to the desktop, and attempt to login, it does exactly the same thing, the same stupid question or requesting for another device. So it gets into a loop of devices which can’t be resolved. And for this other user I tried to setup TB for, they don’t authenticate near often to google, but they use both desktop TB and K9 quite well.

    For now, for such users, until they figure out how the hell to login to their google account again, they better don’t try migrating to Thunderbird, since the import functionality is not quite enough to get google mail working fine, again if the user doesn’t login to google often. A bit sad, though it makes sort of sense, since the apps registered to google would be different. Sad in the sense that an already working setup for gmail on K9 can not just be imported as is to TB, and keep just working.

    While K9 remains working, there’s no issue for such users though. Hopefully that doesn’t happen,

    It works great when not having a google/gmail account, :)


  • Ohh, it needs to import though. I was afraid in case there would be sort of two different directories over the same data, or that on TB dir it would be to start fetching stuff. But it seems it literally copies over the directory contents, which is fine, since the then the other app could easily been removed.

    And it works with TB non beta, I guess it works with beta for testers a well (though I like the release, and see how it goes). I’ll be using non beta for now, a bit behind, I prefer to use releases rather than beta releases, and on f-droid I enabled unstable upgrades…

    Anyone played with push vs. pull on TB? On K9, I ended up having both. With the last years changes, it removed the push option selecting from the fetching configs, but the push could be selected/deselected from each folder, and I keep them both. Pulling makes the requirement of not having restrictions on battery usage though.

    Not sure if that’s getting any better with TB (non beta or beta), and if push has gotten any better. In the end, imap push/idle pretty much depend on the server, and not so much on the client I’d guess…

    Thanks !



  • OK, many thanks !

    I’ll just do nothing for now then. I hope if at some point a migration is required, it’s sort of automatic, f-droid just starts using the Thunderbird app rather than the K9, without user intervention other than performing the f-droid upgrade, one and that would be it. But we’ll see.

    If you ask, knowing it’s the same thing, I would have gone with just one app, replacing the other one, and that would be easier and clearer, :)

    Thanks a lot again !





  • Oh, you mean using divestos-fdroid-repo? Well, before it became part of official f-droid I used to do that. I’m not sure how long it’ll take to fix the official f-droid.org builds though, since I’d like to go back to it. The sad thing is that to move from one repo to another one loses all configurations/settings, :( But perhaps it’s truly unsafe to wait until the build on f-droid.org gets fixed, if it ever does it.

    Anyone aware if there are efforts to get it back building for f-droid.org? Does it depend on the Fennec issue getting resolved?


  • I use mull from f-droid, and f-droid started showing that when upgrading Today to version 1.21.1. No idea why until this f-droid app upgrade.

    I guess the mull issue is the same. Both fennec and mull are at the same version on f-droid, 129.0.2, and both show in their anti-features that the app contains a known security vulnerability, indicating firefox has fixed several security vulnerabilities since 130.

    Is it right to hope that once fennec can get distributed on f-droid, then mull will follow? I’m not planning to move away from mull.

    Thanks !


  • I agree ! I just pointed out the actual differences. And if you use LOS4uG, you have several options, keep F-Droid as it is, keep it and remove the privileged extension, remove it in favor of the basic version, and on top of the last option see if the unattended updates can be opted out/in.


  • kixik@lemmy.mltoF-Droid@lemmy.mlFDroid vs FDroid Basic
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 month ago

    Regarding android version, I think @boredsquirrel@slrpnk.net already gave a good hint. Currently f-droid version 1.21.0 supports android 6.0+.

    According to f-droid basic URL:

    NOTE: The Basic version of F-Droid Client has a reduced feature set (e.g. no nearby share and no panic feature). It targets Android 13 and can do unattended updates without privileged extension or root.

    I don’t see the target version varying between them, I found both to be 1.21.0 on Android (I have enabled unstable updates), and both indicate they support android 6.0+. So if you have LOS or plain android on a version 6.0 or beyond, f-droid should be able to install and work on them.

    I use F-Droid since it comes pre-installed and with privileged extension set by default on LOS for MicroG, so I don’t find it particularly appealing to install F-Droid basic instead, but if that were not the case, I’d go with F-Droid basic, given I don’t set F-Droid to serve nearby devices on any phone, and I haven’t ever thought of using the panic feature. I’m using LOS4uG 21, meaning android 14. with no issues, so perhaps 1.21.0 already target android 14, and not just android 13.

    So I believe both, the basic and the not basic versions of F-Droid target the same version, and support the same versions, the difference is in basic with a couple of less features. But you can always take a look at the version, and there you can tap on the specific version to see what versions of android are supported.

    Greetings !