Getting Help on Buildapc I.R.C.
[1] Don’t ask to ask.
[2] Be precise.
[3] Tell what you are doing.
[4] Read the /topic.
[5] Do not be demanding.
[6] Do not /msg people without asking.
[7] Unintended rudeness.
[8] Do not repeat yourself.
[9] Speak english.
[10] Don’t be lazy – read the documentation.
[11] Give others a chance to answer.
[12] Stay if you can.
[13] Answer the questions that you get asked.
[14] Tell others about the solution.
[15] Be careful who you trust.
[16] Do not flood the channel – use Pcpartpicker.

Build help specific (New/Upgrade):

[17] Tell us where you're from.
[18] Be upfront with your budget.
[19] Be clear with what you want to achieve.
[20] Show us what parts you want to bring over.

IRC (Internet Relay Chat) is a real-time chat where you can talk to other people from around the planet. Although many channels deal with smalltalk about the weather, girl-friends and politics there are IRC networks and channels that are dedicated to provide support for a piece of software or an operating system. for example exists to support open-source projects. In case you need urgent help or just don’t want to use a mailing list then you are welcome on IRC. IRC has been there for ages and has evolved with the time. So it may appear a hot tub of completely mad people at first. This article is meant to help you understand how to IRC works socially and how to get the most out of it.

[1] – Don’t ask to ask.

It’s a bad manner if someone enters a channel and asks “May I ask a question?” or “Can anyone help me?“. Although that may be polite in normal human interaction it does not work that way on IRC. You are supposed to just ask your question right away.

[2] – Be precise.

There is nothing worse than “My computer doesn’t boot.” or “I get no display.“. How are others supposed to help you when you don’t give them any information? Make sure you include at least this information:

What did you try to accomplish? (“Assemble my gaming computer.”)
What has happened (wrongly) instead? (“But my system boot loops.”)
What parts are you using? ( permalink.)
What did you try to find the cause? (“I’ve already breadboarded the system.”)
Are there error message or log files? (The error message reads: “Operating system not found.”)
Has it ever worked? What did you change? (“I switched storage but now I get no display.”)

If all this information is included then you will have a high chance of getting a useful reply.

[3] – Tell us what you are doing.

Others only know what you tell them. If you change things silently then nobody will know about it. The worst thing you can do is say: “I changed something. Now I have another problem.” This will get you ignored in no time. If you expect help you need to work with the supporters.

[4] – Read the /topic.

Your IRC client will likely show you the “topic” of a channel when you enter it. You should find some useful information about how this channel is supposed to work. Often the topic even lists URLs for FAQs and documentation. Asking something that is clearly answered in the topic is very stupid. If there are FAQ URLs listed in the topic first look there if you find your question answered.

[5] – Do not be demanding.

Do not expect a single person to stay online until your problem is fixed. IRC is a stateless medium. Anyone can quit at any time. People stay there because they like staying there. Nobody is paid for helping you.

[6] – Do not /msg people without asking.

You can either talk to others in a channel publicly or /msg them privately. However the latter is considered rude. Don’t occupy a single person for your purpose. Others may as well be interested in a solution to your problem, too. Additionally public help allows for additional information to be added/corrected.

[7] – Unintended rudeness.

Sometimes you may feel that others are rude. You may get a response like “Reinstall the package. Restart the service. Read the /usr/share/doc/mysoftware/README.” Although this is a very brief reply it is likely not meant to be rude. IRC is often like human interaction without all the friendly bits. Other people have probably answered your question a dozen of times today and they just want to help you solve the problem – not become close friends with you. Don’t be offended by it. The people don’t mean it.

[8] – Do not repeat yourself.

Asking the same question every minute is annoying. If anyone in the channel isn’t paying attention then they will neither read you the second and third time. And those who came back from lunch or sleep will likely see in their “lastlog” what has happened lately. This is too demanding.

[9] – Speak english.

In most channels the only language spoken is english. There are certain local channels like #debian-fr which are specifically for frenchmen. But everywhere else you must not write anything but english. It doesn’t matter if your english is bad. Most people in the world speak something different than english, too. And if you find another person that speaks your language then do not start to talk in your local language. Nobody else can follow you and it’s considered rude. Additionally if you live outside of the U.S.A. you should disclose where you live due to the differences in parts availability and pricing internationally.

[10] – Don’t be lazy – read the documentation.

If people tell you to read the documentation then you should do so. Never say: “I’m too lazy. Come on. You all know what I need to do. Just tell me what I need to do.” This will get you ignored for all eternity. However you can expect to be told where to find the documentation. But if you get an URL then get it and read it. If the documentation is too technical or you don’t understand certain sections then say: “I have now read chapter 3.1 of the URL you gave me and I understand how virtual domains work in general. But how would I use both virtual and non-virtual domains together?”

[11] – Give others a chance to answer.

Even if you are in a hurry you should allow other participants some time to answer. Sometimes you are lucky and a helpful reply appears within a few seconds. But it is not uncommon that you will have to wait 10-20 minutes until the right person who is familiar with your problem talks to you. The pattern looks something like this:

10:07 Foo joins
10:07 Foo> How can I install the shripdibble module?
10:09 Foo quit

Then at 10:14 an expert on shripdibble joins but can’t help you any more because you gave up too quickly.

[12] – Stay if you can.

Using IRC is a matter of give and take. At the beginning you will surely you’ll have questions over questions. Just ask them and be grateful if you get attention and replies. Others do not expect more than a “Thank you.” for their help.

If you can, please consider staying online in the channel. The more knowledge you gain the more you can help other people. And you probably get to know people you like to hang out with – even if it’s just virtually.

[13] – Answer the questions that you get asked.

It may sometimes be hard to follow all the conversation on IRC. But if people are trying to help you and need to ask you a few questions please answer them all. If you get asked three questions and only answer one or keep asking the same question time and again (showing that you don’t read what you get asked) you risk to be ignored. Show some initiative and your problem will likely be fixed within a few minutes.

[14] – Tell others about the solution.

It doesn’t help anyone if you just say “Nevermind, found it.” and quit the channel. Please tell the others what the solution to your problem was so everybody can learn from it. You will not look stupid – trust me.

[15] – Careful who you trust.

When getting responses be careful who you trust. Some people just want to feel important and reply to you although they have no more clue than you do. Perhaps even an “educated guess” might help – just make clear if it’s something that was tried and worked. Some people are even jokers who want to be funny by telling you how to erase your hard disk. So verify others’ proposals instead of applying them blindly. Asking for help through private messages opens you up to poor advice that cannot be corrected.

[16] – Do not flood the channel – use pcpartpicker.

Sometimes you need to show others more than one line. Perhaps parts of your configuration files or a log file. Never just copy and paste larger amounts of text right into the channel. Always use a pastebin(or Pcpartpicker for things like parts/builds). Pastebins are public services (websites) where you can paste your text and everybody can access them as a URL. Just paste your contents there and send the URL into the channel. That should allow everybody who’s interested to take a look. Just don’t paste it without any comment. Rather say: “Emails seem to get lost since I installed program foobar. Please take a look at my logs: http://…”

[17] – Tell us where you're from.

Not everybody lives in the U.S.A. its hard to give real advice about parts/systems without knowing local pricing, avaliability and taxes.

[18] – Be upfront with your budget.

One of the first pieces of information you should disclose is your budget as this has extreme effects on what you can use. Additionally saying 'as cheap as possible' will only result in systems that are unfit for purpose or have major flaws and saying 'no budget' will just lead to choices that hardly make sense. You should expect to spend $300-$500 on a basic web/office system, $500-$700 for a basic gaming system and $900+ for a high end gaming system.

[19] – Be clear with what you want to achieve.

We're not mind readers we can't help get an appropriate system put together if you don't tell us what its for. Keep in mind that systems for different purposes require vastly different requirements. Gaming requires a modest CPU and a powerful graphics card, Autodesk products typically require strong single core preformance and V.M. test beds require strong multicore preformance as well as lost of RAM. Its also good practice to disclose what software you're using as well as what sort of workloads you will be running withing them (for gaming the games, monitor resolution and settings are good start).

[20] – Show us what parts you want to bring over.

Bringing over existing parts is a good way to help keep prices down. Make sure you either provide a direct link to the system specs (if its a prebuilt) otherwise use Pcpartpicker and fill out the entire system (use custom parts if you can't find somthing).

Adapted from