Ask HN: How to protect our service against fake requests/trolls?

Re:Ask HN: How to protect our service against fake requests/... by darrennix on Wednesday April 08, 2015 @04:49AM (#9339430)

It sounds like you would benefit from offering a menu of registration choices: - Facebook / Twitter / Google - Email+ other

As with AirBnB registration, you would strongly encourage users to register using a social media auth but allow them to use an email + nothing else if they desire.

You can then apply a simple risk scoring model that says (I'm simplifying here):

* Facebook + 200 friends + > 3 year account age = auto-approve

* Email only = red flag; manual verification

Critically, you don't reveal to red-flagged users that they've been placed in a sandbox.

[ Parent | on HN ]

Re:Ask HN: How to protect our service against fake requests/... by sgb_QQ on Wednesday April 08, 2015 @06:33AM (#9339793)

That's an interesting idea, thanks. We wanted to avoid any concept of registration (ie all appointments are currently 'checkout as guest'), since it's an experience barrier, but Fb/Tw/G+ are good human verification tools.

[ Parent | on HN ]

Re:Ask HN: How to protect our service against fake requests/... by sebie on Wednesday April 08, 2015 @06:09PM (#9344412)

Genius idea. Not OP, but might use for my own projects :)

[ Parent | on HN ]