<<Rv8 writes>>
Do I understand correctly? You went to all the trouble to switch your site from one CMS to another, because you wanted a certain feature, but you didn't take the time to figure out whether that feature was in GL first. And now the developers are supposed to drop everything they are doing and solve your problem.
My 2cents. With all respect, I think this is a undeserved flame (albeit a low-heat one) of a user making a valid comment (about comments). I think you have to forgive their tone. We users aren't usually developers, and when it seems like things are an obvious need being overlooked, it's easy to sound pissy about it.
I meant to mention the comment moderation too. Sure, nothing at the DB level is trivial, but with your rights system, neither should it be particularly challenging (or so it seems). I think this falls into that "core need" bucket that deserves serious attention. CMS users are often community builders, and good community requires moderation. Anything and everything that promotes, faciliates or controls that should get a lot of programmer mindshare, IMHO.
As for the user suggesting an enhancement, please make note of the fact that before finding this comment, I was searching for just where such an enhancement request would be made. In most systems, the forum handles them. Here, as we know, we have no forum yet, but if you look over at that nifty nav column on the left, you won't see any section for "Feature Requests" or "Enhancements."
But you do have a vague and confusing heading called "Got Geeked," which is cute, but means nothing to a new visitor. They have to think about it, and deduce only after looking at all the other sections, that it's probably a place to praise the product, or talk about new experiences. "Geeglog" is equally ambiguous. Why not "Geeklog Discussion, General, Free for all, Random Thoughts" or anything other than the meaningless heading you have presently. In my view, such ambiguities are a disservice to your new visitors, image and effectiveness. But not nearly so much as sounding irritated with a user giving you some valuable insight about a potential oversight or low priority. All such testiness does is discourage commenting and rebuttal. Many users (and people in general) are comment-averse anyway, and can be rather thin skinned, thus, they will avoid saying something potentially useful out of fear that the big, bad developers will be insulted, and they will be embarrassed, humiliated, or might get short-shrift in the future when they have a serious problem.
In my experience with my million-plus users of an instant message application over the years, the very best ideas or feedback often came from the emails that began with lines like:
* I've had it with this POS product. I'm just so...
* I want a refund!
* You people must be brain dead...
* What the hell were you thinking?
* You probably think this is stupid, but....
* I hope I don't hurt anyone's feelings, but....
* I don't know if this is appropriate..
Sure, 75% of the hate mail comes from people too lazy, or stupid to RTFM. But that's just a given in our industry. There are some that feel, as I do, that the manual or Help button should only be required in extreme circumstances, or when nested detail is required. A good GUI should remove the need for it whenever possible.
I just feel it's always a good idea to try and divorce yourself from the user's emotion (and your own). There are diamonds in that rough to be found.