Redjard

The offline version is on izzyondroid.
The design is worse, yes.

I don’t think it matters much because most of the time you only see the autofill thing, not the app.
When you do go to the app, it is to select between multiple credentials, which is still a split second action.

On mobile I have my 2fa in a different more convenient app (aegis), though k2a does allow to copy 2fa codes

It doesn’t.
Both DX and K2A-O open a local keepass file.
They are capable of reloading the file when it is changed, and can be set to immediately write out changes to the file.
Then you take whichever file sync tool you like and sync it with all other devices using it. As long as the sync tool can sync files in your internal storage, it will work.

I use syncthing, with a dedicated keepass folder containing only the database file. Then I simply add all my devices to the share and it’ll sync any changes to all other devices. I also have version history enabled for the share.

Keepass2Android Offline also works very well. It has a somewhat different feature set compared to DX.
I found it to be more stable at remaining permanentl unlocked, and DX dropped the 3rd domain level for password matching on either websites or apps, I don’t remember.
On the other hand DX works better for adding new credentials or making changes. Since I usually do that on desktop it doesn’t matter much for me.

They were doing the same on other repos for months.
Both their npm module and android client.
On android they tried to get people to add their own fdroid repo because the official fdroid has not had updates for 3 months due to the license changes.

Edit: Looking at it now compared to 4 days ago, they apparently got frdoid to remove bitwarden entirely from the repo. To me this looks like they are sweeping it under the rug, hiding the change pretending it has always been on their own repo they control.

Next time they try this the mobile app won’t run into issues, the exact issues that this time raised awareness and caused the outcry on the desktop app, which similarly is present in repos with license requirements.

If they were giving up on their plan, wouldn’t they “fix” the android license issue and resume updating fdroid, instead of burning all bridges and dropping it from the repo entirely, still pushing their own ustom repo? Where is the npm license revert?

Also important to note is that they are creating the same license problems in other places.

They broke f-droid builds 3 months ago and try to navigate users to their own repo now. Their own repo ofc not applying foss requirements, because the android app is no longer foss as of 3 months ago. Now the f-droid version is slowly going out of date, which creates a nice security risk for no reason other than their greed.

Apparently they also closed-sourced their “convenient” npm Bitwarden module 2 months ago, using some hard to follow reference to a license file. Previously it was marked GPL3.

It means previous versions remain open, but ownership trumps any license restrictions.
They don’t license the code to themselves, they just have it. And if they want to close source it they can.

GPLv3 and copyleft only work to protect against non-owners doing that. CLA means a project is not strongly open source, the company doing that CLA can rugpull at any time.

The fact a project even has a CLA should be extremely suspect, because this is exactly what you would use that for. To ensure you can harvest contributions and none of those contributers will stand in your way when you later burn the bridges and enshittify.

What is the threat szenario?
If you are smart about parallelization and have access to custom hardware, couldn’t you turn 5 days into 1 hour or less?

background: #f0f

It appears they just did, as of a few minutes ago while I was looking into it

Here is the now open private components repo under the CC BY-NC-SA 4.0 license
And I forked it just to be sure

1.18.0 doesn’t show that for me, neither does 1.19.0

The version update notes said “removed because android doesn’t do that anymore” or something like that. It might depend on the android version, which is extra stupid because many roms don’t enforce that restriction, and you can mod that restriction out if you have root (which is part of many general root/lsposed modpacks).

I am running A13, but I was running A10 before and that didn’t show it either

In my experience that is quite rare though. Probably less than 10% of the downgrades you’ll do will actually not work.
On the other hand if the app has important data you want to preserve, the other ways of doing so are a) hunt down the apk manually, with the fdroid website not having a convenient download button for older versions, or b) use something like neo backup to make a backup, uninstall, install the older version, and revert the backup except the apk. Both are 1 minute for what could be one button press.

Edit: looking at the fdroid page the download buttons are there now, still you need to search up that page, it’ll probably still take a minute using that method. Why use fdroid if you need to google apks like a caveman in the end anyway?

Then make it an option in the experimental section of the settings.
If an app cannot accept the updated data, if it has even been launched in the new version, the worst that can happen is that it doesn’t work. You can still uninstall, or you can clear the data. You can also pop up a warning before downgrading, explaining the possibility of needing to clear the apps data.
It is still an essential feature for many.
Uninstalling and reinstalling is not only inconvenient, it can also change values like the apps id, that can be essential for advanced users.

For me, the app had an update that removed a feature I relied on without replacing it, making it worse as a result. This therefore makes a valid example to the point made above, that people may not enable automatic updates because updates aren’t always better, sometimes they make an app worse.

Not long ago I watched the fdroid app itself enshittify.
I was testing an update of another app, saw it didn’t really work yet, went to roll it back, and the downgrade button was gone. So I tracked down why and found fdroid had removed it. So I went to downgrade the fdroid app and the downgrade button was gone …
Had to hunt the bare apk and downgrade manually.

I’m still on the old fdroid version procrastinating looking for an alternative.

They are using repeatable builds, so the fdroid version is signed by fossify. You can update between github, izzy, and fdroid, and in the future likely also google play, if they release there.

I dug up the meta discussion on it. Mentioned there is the issue to add reproducible builds to the phone app, which is marked complete since that was released on github and izzy last week.

Further for me the app is marked installed on both entries in fdroid, which means the fdroid and izzy repos should serve bit by bit identical apks, from my understanding (the installed mark being based off of the apk hash).

They are using repeatable builds, so the fdroid version is signed by fossify. You can update between github, izzy, and fdroid, and in the future likely also google play, if they release there.

I dug up the meta discussion on it. Mentioned there is the issue to add reproducible builds to the phone app, which is marked complete since that was released on github and izzy last week.

Further for me the app is marked installed on both entries in fdroid, which means the fdroid and izzy repos should serve bit by bit identical apks, from my understanding (the installed mark being based off of the apk hash).

You heard of standby and the likes? What do you recon that does to programs calculating with time in that exact moment?

Maybe he automated it?