@Thenomain said in Wiki best practices:
@ixokai said in Wiki best practices:
Type '+wiki/password' in game. Receive the word: 'transgoggle'.
Easy. And staff doesn't have to do anything ever again and no bot or spammer will ever get it.
Sending password over clear-text is never, ever a good idea.
edit: I should amend this, knowing that I took one bit of information from a wider discussion and jumped on it. I stand by this statement: Don't send passwords in the clear.
I could not disagree more. If it were a real password or an actual valuable resource, sure, but its not. Its a password that everyone who is approved has access to: its not really even a password. Its something which has no purpose but to make it so people can make accounts with some bit of information obtained in-game that establishes themselves therefore as a) not bots, b) not spammers.
That's not to say that this system can't still be easy, but it should require a two-factor system such as email. Register and verify an email, and then when someone types '+wiki/password' it starts the process via the registered address. It still doesn't involve any third party, which is easier and is good.
Oh, hell no. Asking for an email address is a nonstarter. There's too many people who will not give it-- and they shouldn't have to to play a freaking MUSH.
Dear lord you're making this complicated. It's a wiki for a MUSH. Worst case scenario someone creates a character, goes through the approval process for the diabolical purpose of err, vandalizing our wiki. At which point we shrug, ban them, and revert the changes.
There is also a fantastic wiki plugin called Extension:ConfirmAccount which also involves zero staff involvement.
How does that involve zero staff involvement? Quote the page: "and requires the approval of new accounts by a bureaucrat."
Mind you, these still involve work and our hobby puts a lot of stress on the overhead of game creation to begin with. Until someone creates this for public consumption, it's more something that might be done sometime. For this reason I prefer Extension:InviteSignup, as while yes it involves staff it's quite minimal, can be handled by anyone with wiki-staff, and will give your coder time to come up with something better.
How is this any better?
You're defending against some diabolical site admin attaching a snooper to a telnet session to see the super not even vaguely secret 'password' to create a website by... adding various levels of work for varying people for what reason again? What is the actual benefit to any of this complication?