Following "The 7 Essential Questions of Every Beta", what should our faq contain?
This meta kind of starts the discussion, but perhaps we should have one place to sum it all up with a list of "good" and "bad" topics to put in the faq.
To start things off, the faq should contain :
Here's how the list would look from my perspective. I had accidentally closed the tab with my original proposal, so I had to write it up from scratch and probably left out some stuff I considered important in the original (my commentary on the existing answer was a bit more chatty for example).
In my opinion most of the original (or edited) proposals need further qualification not to blur the scope of the site unnecessarily.
For example I think that the original software analysis is a bit too broad. Of course it is a proper superset of what I am describing, but an FAQ should be more to the point than that in my opinion.
As you can see I also took the liberty - after all this is a discussion - to qualify "hardware" further, and thereby limiting the scope.
Concerning vulnerability research I think it is a fine line. Agreed, most reverse engineers (as in RCE) will have experience with it, but this doesn't mean it strictly falls inside the scope of this site. But this is just one opinion inside a discussion. I'll bow to the majority vote anyway, so if people feel this ought to be the place for vulnerability research questions as well, so be it. I just think it might contradict the idea of splitting topics and creating new SE sites.
Now edit away or comment on this answer :)