Hacker News new | past | comments | ask | show | jobs | submit login

I hate it when companies make these decisions without warning the customers. Even if they are doing something against their terms.



From what I gather, this was the first meetup being organized, and the first meeting was in part to promote a product. This should raise red flags. Otherwise, it becomes a wonderfully cheap spam vector. (Meetup sends noticed to users when local grous are added that users say they are interested in).

As a user of Meetup.org, I'm find with this level of oversight. As long as he can go about getting the meeting reestablished, I see no harm being done, and everything working appropriately.


Well, it's certainly very annoying, but think of several circumstances:

* Hacked account. I actually, upon reflection, did not mind that Google shut everything down of mine when they labeled a blog as spam. What if it were spam written by someone who had hacked into my account? The key thing here is to make it very easy to prove you're you and get back in. And apologize profusely, and explain what it happened. I got everything back but the blog as soon as I confirmed an SMS'ed code. They did take more than a week to get the blog back on line, which was annoying, even if it was nothing important.

* Actual spammers would love to be able to test the boundaries and get quick feedback about what's going to work and what's not going to fly. They'll use any feedback you give them to improve their spamming techniques.

So... it's not easy. I think what pisses me off the most is that there's no appeal, no way to say "woah, I didn't do anything!"


Amen. Kicking a customer should be the absolute last resort, not the first step.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: