I have never liked marking solutions as solved, it limits and often prevents more and better solutions from being presented. This is especially problematic with novices who flag poor solutions as being Solved. However, the Solved prefix is going to be especially problematic with the new philosophy of one programming forum, with the prefix describing the problem type. For example, if I'm interested in Shader topics, I can click on an existing Shader prefix and all the topics with Shader prefixes are displayed. That's pretty convenient, At least until the question or problem is solved, at that point the OP might change the prefix from Shader to Solved. Now, that particular topic will not be displayed because it no longer has the Shader prefix. Ironically, for those who specifically want to use the prefix because they want to learn a subject matter will only see unsolved questions and problems, completely defeating the purpose of the topic/catagory prefix in the first place. As I said earlier, flagging topics as solved, really isn't as benifical as people make it out to be. But if they absolutely must, they can still place a [Solved] in the topic title. Although, I think the best approach is a new post indicating and thanking the solution provider, thus encouraging alternative and better solutions and followup discussion. @Nocturne said in another topic While I like the idea of less forums and given the current traffic, I agree that one forum is sufficient. Given enough traffic than a single forum will simply not be sufficient even with good prefix usage. But as described earlier, the prefix can not be dual usage, ie content descripter and solved indicator. You're going to have to make a decision on exactly how the prefixes are to be used.