I don’t think this is Lemmy’s fault.

All they did was use the more secure SHA256 algorithm.

AFAIK this issue is the result of 2FA apps not properly setting the algorithm as specified (or in some cases not even supporting it)

On the rare occasion I need that, I just run KeePassDX Portable from a flash drive.

But really it’s a bit risky to use any password manager on a device you don’t control.

At least my KeePass database is secured with my YubiKey so it’s not likely anyone will get in if they do stumble onto my DB file.

Ah yeah you are right, it makes me tap my key every time I open the app.

The biometrics seem to only replace the master password.

I do wish it worked more like KeePassXC where the key is only needed to save the database after unlocking and confirming with fingerprint

KeepPassXC can do this as well, but it does require the yubikey to be inserted every time you want to save a change to the database.

Look under Settings -> Security -> Convenience -> Enable database quick unlock (Touch ID/Windows Hello)

Using that I can quick-unlock my database using my laptop’s fingerprint scanner, just like how KeepPassDX works on Android.

YubiKey works for me, both on desktop with KeePassXC and on Android with KeePassDX to the same DB

Actually this is only on Google Collections which is a bookmark sharing service, not just the browser bookmark sync.

Your synced bookmarks should be unaffected as Google says everything in browser sync is encrypted locally before being synced, so Google shouldn’t be able to scan those (or really care about them at all)

They are doing it to protect themselves from legal liability specifically because of the public-facing nature of Google Collections bookmarks.

They don’t care about your synced bookmarks or browser history because it’s not public-facing and they aren’t legally liable for the contents

I think what they meant is that one option uses network connectivity while the other functions entirely offline