Should we put a caution on the longevity of answers? There are questions already about encryption and about legislation, both of which change with time (for instance, only a few years ago SHA1 and MD5 didn't have any known weaknesses; a couple of years before that SOx didn't exist). However, the problem is mainly going to affect "drive-by" visitors who google something like "best algorithm and key size to encrypt a document" so the FAQ may go unread by exactly those people. I don't know.
With the increasing use of social media mining tools such as Maltego we should be stressing that people should think carefully about what they are asking questions on. Especially if they are asking questions about their companies security posture or configuration.
If I was going to do a profile of a company there could be some rich pickings in this site as it develops.
What kind of questions should I not ask here?
Avoid asking subjective or argumentative questions. If you must ask a subjective question, make sure it meets the six guidelines for great subjective questions, or it will be closed.
This would be better put the other way around, I think (with thanks to AviD for suggestions in the comments):
What kind of questions should I ask here?
[...] As many aspects of IT security boil down to interpreting policy or choosing an "appropriate" level of protection/risk, discussion-type questions are acceptable here. They must be on-topic and meet the six guidelines for good subjective questions. Subjective questions may be edited by other users to yield questions that can be answered objectively; those that cannot may be closed.
Adding this here too so it isn't missed. Questions about virus removal of specified viruses: Is it a right place to ask about viruses?
I think we should have something in there specifically around not posting requests for ways to hack a device/app/database/OS. Haven't yet thought of appropriate wording (It is 1am and it has been a long day) but after having to close a couple of questions on this topic I think it is worth having a standard FAQ answer.