Well.. i think a file FAQ tab/area will be great… Editable only by the file developer…
The comment area will still be good for questions/messages that are not yet present in the faq area…
This way you can put an order in the things that are important there. Support facts/conditions; troubleshooting; help; etc
I know this issue is a lot bigger of a deal for authors like DS with huge portfolios. The comment about needing a fulltime comment guy for your files probably isn’t too far from the truth.
I like the idea of improving the comments, but I just can’t get behind getting rid of them altogether. They are too important to the community. Of course the authors will come back regardless, but the vast majority of our members aren’t authors. Like Bobocel said, there are entire communities built around each file. Comments keep people coming back and in turn make authors more money.
Comments are also too important to the potential buyer. People are hesitant to buy things they don’t fully understand. Descriptions tell a lot, but people want to hear the experiences of others.
That being said, I love the idea of making the file pages more useful to both the developers and the buyers.
Yeah, I have to agree with Lance. DS just recently I emailed you prematurely and after reading comments in your file I was able to fix the problem.
I do understand dealing with the comments and the emails can be overwhelming especially for you. Why dont you just use some code to make some bold/larger/colored text in your description that says something like
“Comments may be used to comment, and discuss the file, but please note I will only issue support through email. If you have an issue you need help with please email me”
This way users can post questions in the comments that others can answer. The comments can still be used for general feedback. BUT you no longer need to worry about reading the comments for support related issues.