@soft_chomps@glitch.social @Gargron you've answered my first question, now: 𝘸𝘩𝘺
@boots @soft_chomps i imagine any orgs or pre-existing communities running mastodon would like to not have everyone sign up manually if they already have ldap
@Gargron @soft_chomps@glitch.social one condition:
do not push this to main repo, only add to main repo ways to extend login functionality easily and have the ldap plugin be on the wiki or something
@boots @soft_chomps that's more complicated, so why
@Gargron i'm not sure! i'm saying "providing corporate SSO solutions" sounds really weird in the context of something to add to the main mastodon repo
i mean, you're the one who owns the thing, but...
i just think that there should be a main repo for the "vanilla mastodon" where you can drop it in and have a social network
and then you can have a "plugins" repo that allows extra usecases, so that the main repo doesn't become filled with...well, stuff for extra usecases
@Gargron while from what i've seen while poking around about this, ldap might be a good idea for some people (maybe a bit more people than i stated, i had no clue people were setting it up in this many areas), we shouldn't turn mastodon into a (japanese toilet/emacs/similar metaphor here)
@boots A plugin system is like lightyears more effort (and headache given we want to keep changing lots of internals for now)
There is quite a number of orgs using Mastodon and I am getting some positive responses to this question
@Gargron @boots implementing a different SSO solution isn't even going to be the answer, because if X is on LDAP, then they aren't going to uplift their whole SSO to move to whatever Mastodon chose to implement. Which is why adding something like this to main is bad, because you'll end up w/ dozens of different specialized authentication methods polluting the main branch.
@boots so is there some sort of better SSO system than ldap?