@aaronpk Say more. What is your mixture and does it involve nuts?
@aaronpk Say more. What is your mixture and does it involve nuts?
@aaronpk I need to introduce you to @balloob and the other @homeassistant folks! I bet they'd love feedback from you. (Also, naming things is so hard!)
@aaronpk uh it is made from purest green.
@aaronpk A bottle a day keeps the doctor away!
@aaronpk may as well get ahead of it and make OAuth 3.0 now. Sounds like the AI mastermind has already figured out how to make it super duper compliant, like, globally π«
@aaronpk I read over your post and a bunch of related links. Really fascinating stuff!
From your post: βAll it takes to turn your website into a FedCM-supported site is adding a single `<link>` tag to your home page.β
Can you expand on this? IndieAuth (mostly) requires two `<link>` elements for authorization and token endpoints. What would a singular `<link>` look like in this case?
@aaronpk am I understanding that in order to use FedCM the RP must perform dynamic client registration with the IdP? I'm unsure of how the `client_id` comes to exist for the RP and not really getting it for the first-sign-in flow?
@aaronpk am I understanding that in order to use FedCM the RP must perform dynamic client registration with the IdP? I'm unsure of how the `client_id` comes to exist for the RP and not really getting it for the first-sign-in flow?
@aaronpk This is great advice but anyone who tried it for me would be sorely disappointed by the extreme lack of refund.
Support for RFC 9421 - HTTP Message Signatures in #curl ?
@aaronpk Must an IP68 rating. One positive side effect of not being easy to repair (full water sealing).
@aaronpk Sorry, but extra sleep???