The proposal fails to sufficiently motivate why existing protocols like OpenId Connect can't be used given that trusting the user's home instance seems necessary with this protocol too. The name also is confusingly close to WebAuthn.
this post was submitted on 09 Feb 2024
32 points (100.0% liked)
Fediverse
17683 readers
11 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 4 years ago
MODERATORS
This looks really odd in relation to other fediverse software; Why /magic and required to be on the root of the domain? Why hard-require routing the domain part of the user ID when .well-known/webfinger exists? Why is there a X-Open-Web-Auth header which the spec only describes as "its purpose is unclear from the code"?
So many questions.
I definitely like the idea of distributed sign-in, Solid did a decent work of that many years ago after all. This particular proposal just looks rather odd.
I agree, and .well-known/webfinger is already largely adopted, we should build upon what we already have, not creating even more standards.
OpenWebAuth has been in use on the fediverse since before WebFinger became so widely used.
Like I said in a previous comment, this FEP was written by reverse engineering the existing implementation. It's still a proposal so it still has to go through a discussion period where issues like this can be worked out and it can be updated
Oh I see. Thanks!
The author wrote this FEP by reverse engineering the Hubzilla implementation. The point of proposing it is to find and answer questions like these.