I could be wrong, but I think Qualcomm designs its own chips and only licenses the “API”, so it would be no difference for them.

I was finally able to find some technical detail on passkeys on FIDO website, and yeah, it actually looks like it’s a real improvement over passwords: it’s simple, uses proven technology (public/private keys), and should be much more secure than passwords.

Also, nothing in the “specs” says I need to entrust my private key with the OS or a third party, which is good.

That said, it seems some OS support is required nonetheless, to show the pin / biometrics prompt (or is it?), and on android at least, I’d need to buy a new device with Android 14 to use a non-Google passkey provider…

I use KeePassXC on desktop and Keepass2Android on, well, android, and sync via nextcloud. They all seem to handle syncing correctly, merging changes made on one side, or showing a notification about a conflict, and KeePassXC can definitely merge the two “conflicted copies” together reliably with a couple of clicks (yes, a no-click solution would be better, I know, but it’s not “manual”). Keepass2Android integrates directly with nextcloud and seems to handle it fine.

The situation can definitely be improved but it’s not so bad for me. Also, two different people should probably use two different database files and not share passwords ;)

Not sure how syncthing handles conflicts, it’s been many years since I tried it.

I use KeePassXC’s browser integration daily and it works pretty well with Firefox (linux), well enough that I’m not complaining, but I cannot compare it with Bitwarden cause I never used it. On Android I use Keepass2Android and works well with autofill, but again, I can’t really compare it.

Something tells me Bitwarden works better, just by virtue of being a commercially supported product, but I have no complaints with KeePassXC & Keepass2Android (KeePassDX works well on android too). Original KeePass desktop client was never great though.

I see, that makes sense and should be more secure, in theory. Thanks for the explanation.

The issue I have is, whether I need to trust a third party with my private key, e.g. Google with Android, Microsoft with Windows, etc. (yes on linux it’s different, but that’s not my only OS).

Also if the private key does get compromised (e.g. local malware steals it), hopefully there’s an easy way to revoke it.

Ok, from a quick search, it seems passkeys rely on some trusted entity (your browser, OS, …) to authenticate you, so, yeah, I’m not sure if I like that. The FIDO alliance website is all about how easy, convenient and secure passkeys are, and nothing about how they actually work under the hood, which is another red flag for me.

I’ll stick to old-fashioned, long, secure, randomly generated passwords, thanks.

From a quick search, Keepass2Android doesn’t have it, not clear if they’re working on it: https://github.com/PhilippC/keepass2android/issues/2099

KeePassDX similarly has an open issue, not clear when/if it will be implemented: https://github.com/Kunzisoft/KeePassDX/issues/1421

Good to know about Strongbox on iOS, though I’m on android so no bueno for me.

I don’t use passkeys so I don’t know. Maybe I should research into passkeys, what’s the benefit over plain old (long, randomly generated) passwords?

+1 For KeePassXC and the KeePass ecosystem. Yes, you need to sync the database yourself, but you can use any file sharing service you like, e.g. google drive, dropbox… or selfhost something like nextcloud (like I do), which for me is actually a point in its favor.

Based on this news, I think I made the right choice back then when I decided to go with KeePass.

What do you mean “no cross device support”? KeePassXC supports Win, Mac, Linux and there are iOS and Android apps available…

As for the lack of cloud and requirement to provide your own synchronization, for some (like me) that’s a feature, not a limitation :)

Didn’t he promote it at some point?

… and execution speed is faster. And they’re both open source. I mean, good thing we have choices, right?

Sure, once you have root on the host system you can pretty much do whatever you want … adding entries to udev isn’t anything revolutionary.

From the article:

Patronscan previously had a system flag for “substance abuse,” but this flag was removed in 2019, according to Mlikotin. Its privacy policy notes a California law that limits its flags to “fraud, abuse, and material representation.”

Silo AI is committed to “open source” AI models, which are available for free and can be customised by anyone. This distinguishes it from the likes of OpenAI and Google, which favour their own proprietary or “closed” models.

It’s funny that a company called Silo AI makes open LLM models while one called OpenAI makes closed ones…

You’re welcome! And yes, I can confirm it works in light mode as well :)

I was reading the site on Android, and it looked dark, but after seeing this comment, I tried disabling Android system wide dark mode, and sure enough it became white like in the screenshot! For the record, I tried with both Firefox and a Chromium-based browser.

McAfee is not Russan, just like Instagram is not Chinese (I thought it was clear enough).

Yes it’s a clear reference to TikTok, which I don’t like for many many reasons, but none of those reasons is why it was banned, it’s because it’s Chinese.

But is not Russian, just like Instagram is not Chinese.

The reference to Minority Report is right in the subtitle:

The social media app might get hit with a federal lawsuit before its ban officially begins as the FTC has issued a warning for possible future crimes.

and apparently the FTC statement includes these words:

violating or are about to violate the law.

I mean, I also don’t really like TikTok and have a hard time picturing an adult using it as well, but that doesn’t mean it should be held accountable for “future crimes”. At least, that’s what the article is claiming…