search

exo-do / nodebb-plugin-restrictor

Restrict IP and email domains on registration
0 stars 1 forks source link

Whitelist #1

Open p-harrison opened 8 years ago

p-harrison commented 8 years ago

Hey guys,

Wonder if you might consider extending the functionality to allow for whitelists of domains/IPs rather than blacklists? Would be very handy for those of us creating private forums.

Thanks for the work, handy plugin!

exomarty commented 8 years ago

Isnt is easier to just block registrations and create categories only accesible for marked group?

p-harrison commented 8 years ago

Depends on the use-case really. In ours, we want to allow as free a sign-up process as possible but only to users at our partner companies. So if I can say any users with email addresses @partner1.com, @partner2.net and @ partner3.co.uk can sign-up without admin input it would reduce the administrative overhead and hopefully improve adoption through ease of access.

What do you think, am I missing any existing options?

PS thanks for replying so quickly!!

On Tuesday, 1 December 2015, marty notifications@github.com wrote:

Isnt is easier to just block registrations and create categories only accesible for marked group?

— Reply to this email directly or view it on GitHub https://github.com/exo-do/nodebb-plugin-restrictor/issues/1#issuecomment-161063735 .

segura2010 commented 8 years ago

hi @p-harrison ! It's a good idea, but I dont have enough time to develop it.. If someone wants to develop it, pull requests will be welcome :)

p-harrison commented 8 years ago

No prob and again thanks for replying! Talking to NodeBB about it as part of the setup so we'll see where that goes!

On Tuesday, 1 December 2015, alberto__segura notifications@github.com wrote:

hi @p-harrison https://github.com/p-harrison ! It's a good idea, but I dont have enough time to develop it.. If someone want to develop it, pull requests will be welcome :)

— Reply to this email directly or view it on GitHub https://github.com/exo-do/nodebb-plugin-restrictor/issues/1#issuecomment-161112345 .