LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
While currently the "report" feature is very useful, I sometimes find the ability not to "track" reported threads a bit inconvenient. Particular it's useful to know whether I reported a "dummy" (I made a mistake in reporting) or it was acted upon.
It's good to know any follow-up action on reported threads, because at least it will keep us aware of how to use this feature and learn from mistakes if we committed any.
A simple list of "reports" submitted by the user in the UserCP would be sufficient, although it would be nice if moderators can "rate" reports (Green = positive (acted upon), Red = negative (not acted upon)) so that at least we can know when to report and when not to.
The other advantage, it might make us use the feature more, since we're not reporting into a black hole.
It's not absolutely necessary, but it would be a good idea.
If someone reports a post, in most cases I'll respond to the user if there's no action necessary, etc.
In other cases, all moderators should be replying to the thread reported on whatever action is taken. But from what I've experienced, most just report and move on, not following up with the outcome of the post they reported.
Thanks Jeremy. I would like to clarify that, yes, a moderator does respond to that thread, but sometimes I lose track of the thread itself and wonder why I did report and what for.
At present the only way to keep track is to manually subscribe to the thread. What I was proposing was probably something along the lines of a small list in the UserCP which gives me my last 5 reports and maybe a "status" indicator like in the LQ bug tracker, but not as permanent (this list can removed after a certain period).
Again, I emphasize that I personally don't think it's an absolutely necessary or urgent feature to have, but maybe something to keep in mind for future upgrades.
Yeah, but the social networking is also not being currently used by too many people. However it's another feature I'd love people to use more.
There's lots of features I wished were used more, but we're in the real world.. hate to say it but most come here for the forums and wiki, wiki for documentation to read, forums for quick answers most likely already in the wiki or those that come cause they enjoy the social atmosphere the forums bring with discussing Linux.