Can I suggest a Dev Blog post today that will kill this security crap in the forums, or the release of a fixed up 2.0.2 ? I don't think ignoring this stuff is the best approach. P.