I'm using Firefox as my main browser and see a lot of websites which support passkeys but only with Safari and Chrome, but not Firefox.

Why is that? Is this because of the market share or the implementation?

Looks like Firefox has some different implementation ways than the other two, according to AuthGear https://www.authgear.com/post/passkeys-compatibility

[–] 15 points 1 year ago

I find general source tracking perfectly acceptable. It does not identify me as a user to any of both parties only tells the target site that users originate from another site.

I find personalized urls or tracking parameters bad. General source channel tracking is harmless for me.

  • source
  • [–] 25 points 1 year ago

    Gute Nachrichten, gleichzeitig nicht aufhören zu werben! Je nachdem wie viele Stimmen im Nachhinein ungültig sind, könnte die Petition wieder unter das Quorum rutschen. Also fleißig weiter teilen und unterschreiben.

  • source
  • submitted 1 year ago* (last edited 1 year ago) by to c/firefox@lemmy.ml
     

    Post text: guerda - Because I found out via try & error: some pages don't find their #passkeys  with #Firefox on #Android, which they just created. This happens if you have a password service as default like #Keepass2Android. Creation works though. Chrome just works.

    Easy solution: setup Google wallet as your default password service, then switch to Keepass2Android again and add Wallet as additional service.

    Do this via settings password, default password service

    This should be a blog post.

    #passkey #KeePass

    view more: next ›