Hi Leetcode\n\nRecently there are bad signs that make us concern about you\n\n1) Falling quality of questions and contest:  bi weekly 29, weekly 196,... you accepted weak test cases, or allowed n^2 when it\'s clearly out of question given the size of the input\n\n2) Unstable env:  In weekly 195 people got massive timeouts and errors...Two days a go premium users got long delays in submission\n\n3) Contests with questions that are easily searchable: Want to single this out because at least you can make the title unsearchable. Tell a story and hide the real problem under it might be a good idea?\n\nWe all want to see leetcode successful. Here are some more suggestions\n\n4)  Let us know more about what you are up to. More community communications about recent events (if you already have one, please point them out to me)\n\n5) Scale up, especially when you have a contest\n\n6) Vet your questions thoroughly. Thnk about what fake solution people may come up with, and design test cases on that direction\n\n7) Like topcoder, introduce "hacking" feature in contest that within 30 min of contest ending, you can peek and provide test cases that will fail other\'s submissions

Hi Leetcode\n\nRecently there are bad signs that make us concern about you\n\n1) Falling quality of questions and contest:  bi weekly 29, weekly 196,... you acc