Redjard

The kde default explorer dolphin does.
It creates them at the root of separate partitions (or maybe only network mounts).
Basically as a fallback to moving it slowly into a local trash.

You probably have the system mounted elsewhere and are accessing it remotely with dolphin would be my guess.

Last time I encountered it I found no good solution, it’s very anyoing.
Best workaround is to create a file of the same name as the folder, that way at least it stays empty.

Needs a none option for base

Oh I misread.
Are you using Android 10+ and the op isn’t?

As best I can tell, Mull is us.spotco.fennec_dos, so on that list.
Mulch is likely us.spotco.mulch based on mulch webview being us.spotco.mulch_wv, neither are on the list.

My interpretation here is that Mulch uses some other system, perhaps that mentioned api or something else entirely. Therefore it needs no explicit mention and just works. It might be that it previously did not support that system, or bitwarden didn’t, but somehow now it does.
On the other hand, Mull still requires the manual compat lsit for whatever reason, therefore now in ironfox you run into that issue. In Mull it was likely solved before you ever used it.

deleted by creator

Maybe bitwarden has a hardcoded list of browsers and defaults to the app id otherwise? There could also be an override, but if not you’d have to open an issue with bitwarden and wait for them to update their list.

Edit:
Looking into the code there is indeed a hardcoded list.
This file contains the code

// Docs state that password fields cannot be reliably saved in Compat mode since they will show as
// masked values.
bool? compatRequest = null;
if (Build.VERSION.SdkInt >= BuildVersionCodes.Q && fillRequest != null)
{
    // Attempt to automatically establish compat request mode on Android 10+
    compatRequest = (fillRequest.Flags | FillRequest.FlagCompatibilityModeRequest) == fillRequest.Flags;
}
var compatBrowser = compatRequest ?? CompatBrowsers.Contains(parser.PackageName);

I read this as:
There are browsers that do “native” autofill and ones that do “compat”. Mull and ironfox do compat.
This compat support is communicated on Android 10+, but either on older android or maybe if the app is built for older android (?) it won’t be communicated, thus the hard coded list.

Doesn’t look like there is a way for users to add to this list.

I see no webview anymore, mulch was the last one I am aware of.

Yeah that seems about right.

I don’t know how the versioning works for the Android versions here…

Android has the same versions as desktop here, which is why there is no differentiation. The main chunk of firefox is platform independent (and even used in thunderbird too).

So any firefox android app and fork thereof needs that version 131.0.3+ too (unless it is esr which is 128 currently).

173? What happened to firefox versions? We just started the 130s

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?

The “BetterHelp” YouTube Virus is BACK

Currently the main repo.
Ideally youd take the definitely broken ones into the archive.
But there is always someone still using them just fine, how could you possibly tell when an app isn’t useful anymore?

Archive is for old versions not old apps. As in if you don’t wanna fiddle with versions you have no reason to enable the repo.
It will only cause casual users issues with not finding apps

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