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 !

Arkenfox user.js, or derivative broswers like Librewolf on the desktop and Mull on android are there for a reason. Firefox default settings are not the safer, although it has all the knobs to make it a much better experience.

For some time the alternative is freetube, though I don’t like is electron, is what we can somehow reliably use

What I post from lemmy.ml wouldn’t be seen there if that were the case, but it’s seen there, so that doesn’t seem the case…

BTW. I’ve already joined… That said, I see the same posts missing. Of course that doesn’t apply to one I made myself from lemmy.ml. There’s also a bot one from 9 days ago, but the rest are at least 1 month old…

pending for subscription, we’ll see, and while pending, still not syncing properly…

https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-23h2 https://www.bleepingcomputer.com/news/microsoft/microsoft-says-april-windows-updates-break-vpn-connections

Perhaps click bait, but based on MS’ own list of issues with April’s upgrade patchset.

I like the SMS gate app from f-droid suggested.

A different approach to read SMS from other devices, for example your PC, would be using kdeconnect. It’s supposed to allow you to read current messages, receive messages, and reply to messages, even send messages I believe. So perhaps an option, though not a syncing tool to keep SMS messages somewhere else, and I can’t tell about the encryption involved…

f-droid -> expert mode -> privileged extension (turned on)

But you need to install f-droid with privileged extension, which is easy on LOS and derivatives/forks, but not sure on things like grapheneOS/calyxOS/pure android…

Thanks !

which one is it? The replies were erased, :(

Pff, I just got logged out on a refresh, hehe. So what I said is not true, I’m getting logged out, somehow randomly (can’t say I know under which conditions that happens). Not sure if there was a release candidate upgrade, since I can’t remember the version before this new logout. Currently:

UI: 0.19.0-rc.11
BE: 0.19.0-rc.10

Nope, I only have a lemmy.ml account, and I only use librewolf on the desktop…

I had that issue of having to re-login, and then every now and then when I do reload, it posts not on my subscribed communities as if I were not logged in, although I’m logged in, but on a subsequent reload, then only my subscribed communities posts show up. I haven’t had to re-login again, just after the upgrade, and then the other minor annoyance is that, but a subsequent reload is enough…

Thanks !

Is it normal that on an upgrade, users are forced to re-login?

Actually to me, this has made Jitsi less of an option now a days, cause when people need to start looking for which instance, then things become no longer as easy… I now recommend instead Jami, which is close to distributed, which is way better, perhaps if people start using for video calls, it gains users base for being the communication app of choice, :)

I have it working with my family, and ti works quite fine. It’s quite easy as well, once the accounts have all been setup…

Setting an account is not hard at all. The complexities come when wanting multiple devices getting in sync. On Android it’s been rock solid for some time already. On the GNU+Linux side, depending on the distro, it might have fatal issues, or just work.

Well, it’s been filed already, and seems to be an issue only on LOS, apparently not for Android, and perhaps not other AOSP based ROMS. See F-Droid Version 1.0.35 Will Not Install

Perhaps, I just read about Obtainium, hehe. Thanks for the hint. At this point I’d like to understand what’s the issue first, because I’d like to still install it from F-Droid (I would do it with obtainium that way), and I can’t tell right now if the issue is on the app, or on the F-Droid build, and to me it’s really curious that the error says “defining” instead of “trying to acquire”, which doesn’t seem like something an app would do. Perhaps it’s just a F-Droid message, and not an app installing one. Can’t tell. But as I’d like to keep using F-Droid, then perhaps it’s good to see if it’s a temporal issue just with the last release on F-Droid, that release of the app itself, or something that will remain.

BTW, I use apkgrabber for a few apps from apkmirror, and obtainium might perfectly be an option…

Edit: Just found out it’s the app having issues with LOS, and therefore LOS for microG. See the edit on my original post. Thanks !

Nope, I only install F-Droid provided apps from F-Droid. When changing that, like when moving Newpipe from the F-Droid provided one to the Newpipe repo, I have to uninstall it 1st.

Now, the issue is not about signature. It’s about “defining” a permission, which BTW, I can’t tell what that exactly means. In my mind defining is not quite the same as trying to acquire, and the later is more reasonable for an app to me, and can’t understand how come an app can define a permission. But oh well, perhaps the error message is not as accurate.