Login
You're viewing the functional.cafe public feed.
  • JadeJadedBlueEyes@tech.lgbt
    Nov 17, 2026, 9:36 PM

    @intarga @Arusekk Organisations are made of people, and different people within them have different motivations. Commercially, they did not need easier acquisition of customers - they already had an incredibly strong lever - and they did not need plausibility. The social logins were extremely successful, so they got resources, and those engineers likely wanted to do the best job they could as engineers - so they focused on security, simplicity, and standardisation (because open source reduces costs makes the world better). So we got many iterations, but in the end we got a much improved Auth component, perfectly shaped for fitting into their social login SDKs. Those SDKs still exist, but they aren't used as much for social login by nature of Conway's law and because they are less private still.

    💬 1🔄 0⭐ 0

Replies

  • JadeJadedBlueEyes@tech.lgbt
    Nov 17, 2026, 9:51 PM

    @intarga @Arusekk so you have an improved auth component! They've done all the work of standardising it, of ensuring it's secure and so on and so forth. So of course other spaces are going to use it! That is why open source is powerful. When you need a way for two arbitrary independant systems to exchange auth with each other it's great! Infinity better than earlier iterations, be that SAML or LDAP quirk stacks or earlier OAuth+proprietary tangles. This system funded by big tech has gone and helped other spaces, even those diametrically opposed to big tech. And I directly use the library that you decided not to contribute to in a project that is antithetical to their dominance. So yes, contributing to that project could help big tech, and people building stuff that enforces their dominance - but it also helps those whos existence is diametrically opposed to it! That's open source! And that's why that paragraph was something that I disagreed with.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • JadeJadedBlueEyes@tech.lgbt
    Nov 17, 2026, 10:34 PM

    @intarga @Arusekk I suppose a part of it is while I agree with a lot of your article, I disagree with both your perception of open source as broken and your evaluation of OIDC as a technology structurally predisposed to centralisation. With that in mind, I think neglecting the libraries we all depend on is how open source is in this bad state - and as the beneficiary, your employer should be contributing by paying for your time to improve the commons. I could talk about this stuff for days and days - I know that it's complicated and subject to disagreement.

    💬 1🔄 0⭐ 0
  • Nov 18, 2026, 11:47 AM

    @JadedBlueEyes @Arusekk

    i don't think open source is broken, i only intend to put more thought into what i contribute, why, and its effects.

    while i'm not going to write an OIDC library, i would still be up for working on decentralised auth, but i would insist on revisiting the assumptions baked into the protocol, for example:

    - is a third-party identity provider strictly necessary? we do have examples of identity attestation without one, i.e. ssh
    - the core/standard claims can go, especially the gender one, with prejudice

    if the identity provider is necessary for a given use case:

    - does the identity provider need to be aware of which service the user is authenticating with?
    - can we build more redundancy and/or migration between identity providers into the protocol, so that any given provider becomes less central and powerful?
    - why is it necessary? i think many services use it as an assurance that a user is a real individual, and not part of a bot swarm. not all providers serve this need equally, and their answers for it typically lie outside the protocol. this favours big providers, and i think it's part of why they see OIDC as furthering their ends, not threatening them. is there something we could do in the protocol to counteract that?

    big providers benefit from these assumptions being baked into the standard and taken as given. by revisiting these, i think i could make something that has the positive effects i want while avoiding the negative externalities.

    the only reason i haven't started on this is that i think good implementations need to be use driven, and i don't currently have a use case. the work project is a non starter since there OIDC is not a technical choice, it's mandated by the provider, that's in turn mandated by management.

    💬 0🔄 0⭐ 0