lka1988

joined 1 year ago
[–] lka1988@lemmy.dbzer0.com 2 points 3 days ago

Newpipe already exists

[–] lka1988@lemmy.dbzer0.com 1 points 3 days ago (1 children)

FUTO has made questionable actions

Such as?

[–] lka1988@lemmy.dbzer0.com 2 points 3 days ago (2 children)

What I don't like is they lock their bootloader

Well that's a major letdown.

[–] lka1988@lemmy.dbzer0.com 2 points 3 days ago (1 children)

It is not possible to actually build this from source, since it depends on proprietary toolchains and sources.

Mfw

[–] lka1988@lemmy.dbzer0.com 1 points 6 days ago

you'll shit bricks

[–] lka1988@lemmy.dbzer0.com 4 points 1 week ago* (last edited 1 week ago) (1 children)

Pixel 9 Pro XL owner here. I love how there is virtually zero information about this from Google themselves except for this one article.

[–] lka1988@lemmy.dbzer0.com 1 points 1 week ago* (last edited 1 week ago)

The beauty of KeePass is that the same KeePass database can be accessed using any KeePass client, regardless of platform, as long as the database version and security measures are supported by said client.

I use various clients, including the OG KeePass client, KeePassXC, Keepass2Android, KeePassium, and KeePass DX to access my database (synced across multiple devices via syncthing and regularly backed up to a separate location).

[–] lka1988@lemmy.dbzer0.com 1 points 1 week ago (1 children)

But KeePassDX freezes at times and doesn’t respond to my taps.

That sounds like a device issue. The A series is Samsung's budget line of tablets, so it was already underpowered from the moment you bought it. I used KeePass DX for a bit on my Pixel 9 Pro and it worked really well... But I wasn't a fan of the interface, so I switched back to Keepass2Android.

[–] lka1988@lemmy.dbzer0.com 4 points 1 week ago (1 children)

I've been using KeePass for years: KeePassXC on my PCs, OG KeePass on my work laptop, KeePass2Android on my Android devices, and KeePassium on my iOS devices. They're all compatible with the same 2.x database version, and all are synchronized with each other via Syncthing.

I've experienced some autofill issues on my Android devices, but that's mostly due to a lack of metadata in those entries. Outside of that, it works great ¯_(ツ)_/¯

[–] lka1988@lemmy.dbzer0.com 4 points 1 week ago

You can still set up a payment method on the watch via Google Wallet even if your phone is rooted. I did this for a year or so with my Pixel watch, before I decided to ditch that for my PineTime watch.

[–] lka1988@lemmy.dbzer0.com 16 points 1 week ago* (last edited 1 week ago) (2 children)

Just because a higher level of security exists doesn't completely invalidate the lower levels.

That, and the physical card your phone uses for funding tap-to-pay is still vulnerable to that same attack, and not everywhere supports tap, and tap only works if you have a functioning device. Not carrying a backup form of payment is asinine.

[–] lka1988@lemmy.dbzer0.com 50 points 1 week ago (5 children)

Just use the card your bank gives you?

view more: next ›