A while back there was a discussion about a master auth server. VanessaE brought up valid points about single point of failure but I want to revisit this again.
The issue I have is that there are hundreds of accounts on my server but many are stale because people don't remember their password. There is no recovery mechanism since people only create a username and password. I would like to have a backend authentication mechanism so that a minetest user could have a profile with email, phone number, etc. to facilitate a web based and/or MMS based password recovery.
This would also allow us to build a community with more interaction. Like right now my server keeps crashing, but a number of the same users keep trying to connect within minutes of restart. Would be great to know who they are for testing and comments.
Also, our K-5 school is interested in Minetest but they want to make sure that it is locked down to only their students so having a password requirement for each world would be great. ACLs would also be a great option.
- *Local Master server for Auth that reports up to Master List Server.
*a. I envision I have a master server for authentication and listing of the different servers I am running which announces up to the Minetest community master listing server. This way there is no single point of failure for authentication, only my server "pod". I am familiar with coding in PHP with MariaDB (MySQL) so would work on that for authentication. Would be better if there already was something built for some other project though we could bring in to Minetest.
* Password by world.