#dev 2024-12-31
2024-12-31 UTC
# havenmatt gRegor: Thank you!! I'll look into the JSON syntax
grufwub, jimw, [KevinMarks], bitauger and Guest6_ joined the channel
# havenmatt Another question about MicroPub as I'm finally getting a bit of time to unpack everything that is happening. The spec for media endpoints (https://micropub.spec.indieweb.org/#response-2) indicates that uploading an object should return a URL. It looks like Quill is then trying to fetch the object at that URL without any authentication. Since mine is a _private_ blogging platform, I don't want it to serve the object without a
# havenmatt [edit] Another question about MicroPub as I'm finally getting a bit of time to unpack everything that is happening. The spec for media endpoints (https://micropub.spec.indieweb.org/#response-2) indicates that uploading an object should return a URL. It looks like Quill is then trying to fetch the object at that URL without any authentication. Since mine is a _private_ blogging platform, I don't want it to serve the object wi
# [tantek] capjamesg[d] re the passkey support in your reader, curious how you avoided the problems described in this article: https://arstechnica.com/security/2024/12/passkey-technology-is-elegant-but-its-most-definitely-not-usable-security/
# havenmatt aaronpk: Great to know, thanks! The follow `create` request seems to be specifying a data URL, which is why I assumed Quill was treating the upload as a failure. Do you know why it isn't using the returned media URL?
# havenmatt https://quill.p3k.io/editor
# havenmatt I'm using that editor
# havenmatt From my server logs: `Completed 201 Created in 466ms`
# havenmatt I'm not logging the location header, but the subsequent GET request uses the correct image URL. But interestingly the GET is from _my_ IP
# aaronpk might be helpful to go through the tests on https://micropub.rocks since that gives you some better debug info
# capjamesg[d] [tantek] I definitely think there is work to do on the UX of the technology.
# capjamesg[d] I wish there was a link to manage passkeys on the iOS prompts.
# capjamesg[d] In testing, I made passkeys for a few different accounts, and now they are all listed in the pop up.
# havenmatt But micropub.rocks doesn't support PKCE!
# capjamesg[d] Of course, that is not representative of a typical experience, but it was a papercut I found frustrating.
# capjamesg[d] I intentionally list password authentication at the top of the login options.
# capjamesg[d] This ensures that the experience most users will expect is above all else.
# capjamesg[d] Given the nascent nature of passkeys, I wonder if I should have an explainer page where you set up your passkeys that explain how they work.
# capjamesg[d] I love the idea of passwordless auth, but honestly I want a password to fall back on.
# havenmatt I can experiment with making images public and seeing if that makes a difference, I'll report back eventually aaronpk[d]
# capjamesg[d] I don't like how 1Password tries to hook in as a passkey provider when my passkeys are saved in iCloud, either.
# capjamesg[d] It's unintuitive to know I need to press X to dismiss the 1Password modal before the OS modal will pop up with my passkeys.
# capjamesg[d] aaronpk Did I do the client.json thing right?
# capjamesg[d] I wish indieauth.com showed the app name 😄
# capjamesg[d] coffee++
# [Joe_Crawford] [snarfed]++ for answering a very basic bluesky api q in https://github.com/bluesky-social/atproto/discussions/2572
Xe and gRegor joined the channel
# havenmatt aaronpk: Oh, good to know! Thanks
# Loqi Solid is an abbreviation for Social Linked Data (originally capitalized as SOLID, sometimes as SoLiD), a web-based protocol designed for decentralized social web applications and Linked Data with features such as single sign-on, universal access control, and a universal data API https://indieweb.org/Solid
# Loqi It looks like we don't have a page for "passkey" yet. Would you like to create it?_c (Or just say "passkey is ____", a sentence describing the term)
# Loqi Web Authentication (WebAuthn) is a W3C Recommendation for an API to access public key credentials, including for a browser, optionally with the use of a hardware key https://indieweb.org/webauthn
# [tantek] webauthn << Criticism of Passkeys usability in particular: 2024-12-30 Ars Technica: [https://arstechnica.com/security/2024/12/passkey-technology-is-elegant-but-its-most-definitely-not-usable-security/ Passkey technology is elegant, but it’s most definitely not usable security]
# Loqi ok, I added "Criticism of Passkeys usability in particular: 2024-12-30 Ars Technica: [https://arstechnica.com/security/2024/12/passkey-technology-is-elegant-but-its-most-definitely-not-usable-security/ Passkey technology is elegant, but it’s most definitely not usable security]" to the "See Also" section of /Web_Authentication https://indieweb.org/wiki/index.php?diff=99366&oldid=90729
# [tantek] webauthn << more usability criticisms of passkeys etc (turn these into citations with the template) 2024-10-14 [https://systemsapproach.org/2024/10/14/can-passkeys-replace-passwords/ Can Passkeys Replace Passwords] / Timely idea faces deployment challenges; 2024-04-08 [https://proton.me/blog/big-tech-passkey Big Tech passkey implementations are a trap]; 2024-09-09
# [tantek] [https://world.hey.com/dhh/passwords-have-problems-but-passkeys-have-more-95285df9 Passwords have problems, but passkeys have more]; 2024-02-08 [https://joshcgrossman.com/2024/02/08/one-does-not-simply-implement-passkeys/ One does not simply implement passkeys]
# Loqi ok, I added "more usability criticisms of passkeys etc (turn these into citations with the template) 2024-10-14 [https://systemsapproach.org/2024/10/14/can-passkeys-replace-passwords/ Can Passkeys Replace Passwords] / Timely idea faces deployment challenges; 2024-04-08 [https://proton.me/blog/big-tech-passkey Big Tech passkey implementations are a trap]; 2024-09-09" to the "See Also" section of /Web_Authentication https://indieweb.org/wiki/index.php?diff=99367&oldid=99366
GuestZero, sebbu2 and bterry2 joined the channel
# carrvo[d] [tantek]++ that passkey read was quite interesting!
# carrvo[d] capjamesg Would the following be an appropriate example of consuming the client.json thing? https://github.com/Inklings-io/selfauth/pull/59
# carrvo[d] [edit] capjamesg Would the following be an appropriate example of consuming the client.json thing? https://github.com/Inklings-io/selfauth/pull/59
# capjamesg[d] I believe so!
# capjamesg[d] I didn't know about the client_tos property!
# capjamesg[d] Good to know.
# carrvo[d] I included displaying the fields I felt were most consumer palitable. Note that I made sure to still include the raw client ID.