Top Document: comp.os.msdos.programmer FAQ part 1/5 Previous Document: Next Document: See reader questions & answers on this topic! - Help others by sharing your knowledge Netiquette is good Usenet etiquette. It includes basic rules like the ones below. (See also <Q:01.11> [How can I learn more about Usenet?]) * Always read a newsgroup for a reasonable time before you post an article to it. * Pick the one right group for your article; don't crosspost unless absolutely necessary. If you absolutely must post an article to more than one group, do crosspost it and don't post the same article separately to each group. See <Q:01.12> [What other technical newsgroups should I know about?] when considering where to post an article. * Before you post a question, make sure you're posting to the right newsgroup; the best way to do that is to observe the proceeding rule. Check the group's FAQ list (if it has one) to make sure that your question isn't already answered there; see <Q:01.13> [Where are FAQ lists archived?] * When you post a question, if you ask for email responses then promise to post a summary. Keep your promise. And make it a real summary: don't just append all the email you got. Instead, write your own (brief) description of the solution: this is the best way to make sure you really understand it. * Before you post a follow-up, read the other follow-ups. Very often you'll find that someone else has already made the point you had in mind. * When someone posts a question, if you want to know the answer don't post a "me, too". Instead send email to the poster asking him or her to share responses with you. * When posting a follow-up to another posted article, remove all headers and signature lines from the old article; just keep the line "In <article>, so-and-so writes:". Also cut the original article down as much as possible; just keep enough of it to remind readers of the context. * Keep lines in posted articles to 72-75 characters. Many newsreaders chop off column 81 or arbitrarily insert a newline there, which makes longer lines difficult or impossible to read. But you need to keep well below 80 characters per line to allow for the > characters that get inserted when other people post follow-ups to your article. * Keep your signature to 4 lines or less (including any graphics) and for heaven's sake make sure it doesn't get posted twice in your article. * Don't post email without first obtaining the permission of the sender. User Contributions:Top Document: comp.os.msdos.programmer FAQ part 1/5 Previous Document: Next Document: Part1 - Part2 - Part3 - Part4 - Part5 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: jeffrey@carlyle.org (Jeffrey Carlyle)
Last Update March 27 2014 @ 02:11 PM
|
Comment about this article, ask questions, or add new information about this topic: