FedCM Versus OpenID: Why Core Identity Standards Are Stuck Between 'Centralized Failure' and 'Redundant Patch'
The core argument revolves around whether current OpenID Connect (OIDC) structures are sufficient for a truly decentralized web or if a new standard is mandatory. Specific technical discussions target the gap between existing federation standards and the need for thousands of unknown identity providers.
Commenters are split on the necessity of FedCM. 'erlend_sh' argues OIDC is 'innately centralized' and insufficient for a massive, unknown web ecosystem. Conversely, 'moonpiedumplings' dismisses this urgency, noting that tools like Forgejo already let users bring their own OpenID links, implying FedCM is overkill. Other arguments muddy the water: 'poVoq' suggests the perceived flaws are user adoption problems, not protocol failures.
Ultimately, the field lacks consensus on the required identity standard. While there is a clear desire for federated alternatives across identity and content (like Loops for video), the technical divide persists between those who demand protocol overhauls (CIMD spec via AT protocol) and those who believe existing workarounds are sufficient.
Key Points
OIDC is inherently centralized and inadequate for a vast, unknown set of identity providers.
erlend_sh strongly asserted this, pointing to the challenge of integrating 'a plethora of small identity providers that cannot be known upfront.'
Existing configurations can bypass perceived OIDC limitations.
moonpiedumplings argued that Forgejo already allows users to 'bring their own OpenID link,' undermining the need for FedCM upgrades.
The true standard for decentralized OAuth is the CIMD specification.
erlend_sh specified that the AT protocol is advancing this standard via its `oauth-atproto` framework.
Upscrolled's features for short-form video are replicable on themed instances.
tofu questioned Upscrolled's technical merit, suggesting its core functions exist elsewhere on platforms like Pixelfed.
Loops serves as a current federated alternative for short-form video.
davel provided a concrete name for a current alternative, identifying Loops (joinloops.org).
Current protocol shortcomings are due to user behavior, not inherent technical failure.
poVoq suggested that limitations are rooted in 'user adoption patterns rather than inherent protocol flaws.'
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.