@jyasskin That's not exactly "state of the art"... More polished applications would give you a screen like the one attached.
But yes, there are still a lot of rough edges. If you care, now is the time to join the Linked Web Storage Working Group 😉
@p20n @jyasskin I wouldn't go as far as stamping "polished app" b/c of publishing a client id doc (b/c it is trivial) but more like expecting 1) each app instance to publish own client id doc 2) clients managing access 3) servers authz those specific client ids
Static client registration is impractical and not a great fit re decentralisation & loosely coupled components (re Solid pitch). That's besides poor UX (though, not Solid-specific).
Solid-OIDC falls short: https://lists.w3.org/Archives/Public/public-solid/2025Apr/thread.html#msg23
@p20n @jyasskin Moved some pixels around and now @dokieli does both static and dynamic registration. Uses dynamic if dokieli.js's origin differs from webpage or in extension, static otherwise. dokie.li website has its own Client ID Document now, but if anyone wants to host their own dokieli script w/ Client ID document, it can also use static registration.
Now we are polished. 😹
PS: #OIDC is still awful #DX and #UX, .. the redirects, and the amount of things going wrong is just meh.