No offence, but I think you answered your own
question:
On 05/12/05, Mischa Peters <mischa2023(a)gmail.com> wrote:
> Could someone explain to me why an email verification of the user that
> is about to edit on your wiki is restricting editing?!
No offence, how did I answer my own question?
It might be considered as a restriction but I don't see why these 2 are related?
Yes it
would... especially since for one project I would like to lock
it down to a specific domain. And opening a gmail account is an
additional step that a lot of people don't want to take.
So, you are restricting edits to those who can or will take that extra
step. Whether that's good or bad is open for discussion, but surely
the fact that "locking it down" is "restricting it" is as plain as
day?
Maybe the definition of "restricted" means something else to different people.
Personally I feel that an email verification is not a restriction.
You can argue that if this is considered a restriction then there are
already a lot of restrictions in place that made it in MediaWiki.
Think, regsitering to the wiki.
Think, disallow edit of a page when a user is not logged in.
Think, read only wiki.
Meanwhile, what do you mean be locking down "to a
specific domain" -
do you mean that you're planning to use e-mail verification as a way
of authenticating that the users already hold accounts on some other
service? If so, out of curiosity, are there other possibilities (LDAP,
checks in a shared database), some of which may already have been
implemented?
That is a good point. I will most diffinately look at it.
Mischa