@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 @soft_chomps@glitch.social because something that no more than like, 2-4 cloners will ever use shouldn't be in the main repo, in my opinion
@boots so is there some sort of better SSO system than ldap?
@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
@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 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)