Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How well does the business.txt standard hold up against malicious behavior? For example, what happens if I want to defame Restaurant X, so I make restaurantXsucks.com and put a business.txt file in my root directory with the same address and contact information? Currently, Google Places (the service that puts stuff on Google Maps) mails a PIN to the address and requires verification before listing to mitigate this problem -- how would business.txt mitigate the problem?


More simply, you're saying that this solves the updating issue but not the trust problem. This is true, but currently it's no better than what is being proposed.

Google places is good but I doubt Yelp does anything, for example, and a ton of other sites. And most people don't even know to trust google places more anyway, they'll just trust the top result on google.


that's a really good question on which i have no answer. I will think about it.

PD: i hate when we have to complicate things because of bad human behaviours!!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: