ulhar4409I do think it a little worrisome that it's passkeys only, but my "main" devices support that, so it's workable for me (besides, in practice I lean towards posting from my phone for some reason)
aaronpki know some people are not a fan of that, but that's also not relevant to the spec, and you are welcome to use a different service that works the way you want!
aaronpkpart of this transition is also trying to be somewhat more opinionated as a service operator and not trying to appear as the "canonical" indieweb auth service. so I don't mind making a few people upset with decisions like that
ulhar4409that feels like a bug, but also, I Do have the option of making my html more simple-stupid (which would make it easier to parse for other software that might also have this bug), so
ulhar4409i wonder if there's any micropub extension that's like, "Here's some bespoke fields we accept that would be 'easy' for you to expose if you simply knew about them"
ulhar4409actually, fussing with type and hints seems overly complicated for an ideally simple feature. so maybe just config.extended-fields.entry = [ content-warning ] (array of fields)
ghorsey_mobile, rMdes, cotsuka, WinnerWind and barnaby joined the channel
ulhar4409The second thing you should do is look for Link: headers with relevant rel values (indieauth-metadata, authorization_endpoint). Here be dragons
ulhar4409in particular I can't think of any reason someone would willingly put ; or , anywhere in a Link header besides to separate what needs separated
barnaby, chimo, marc_in_space, cotsuka, jone75, jak2k, rMdes-bnc, rMdes and oodani joined the channel; jone75 left the channel
[capjamesg]If anyone has any thoughts I’d love to hear them! It’s not published as a blog post yet. I want to make sure I haven’t missed anything obvious before publishing.
ulhar4409Does anyone know of a "native" Indieauth client that uses localhost/loopback as a redirect uri? I'm trying to do that and I'm not sure if I'm missing something or if caching is just being mean to me