Asking someone for help when something goes wrong

Something is not working, so you ask. A friend who is good with computers, a chat group, a forum thread, a support channel, usually with a screenshot attached to save typing.

This card is called self-inflicted because unlike every other page in this section, nothing here happens to you. There is no courier, no housemate walking in, no notification arriving at the wrong moment. You compose the disclosure yourself, deliberately, and you attach evidence to it because you want the answer to be good.

That is also why it is the most fixable. A question you are about to write is entirely under your control until the moment you send it, which is not true of anything else in this catalogue.

What the helper learns, and why they need most of it

Diagnosis runs on specifics. Someone who genuinely wants to help you needs to know what you did, what you expected, what happened instead, and what the exact wording of the error was. Vague questions get vague answers, and the well-known reason threads go round in circles for twenty replies is that the original question omitted the one detail that mattered.

So a helper legitimately ends up knowing: that you use a particular kind of site, which browser and roughly which version, what your setup looks like, what stage of a process you were at, and often the literal text on your screen. If you attach a screenshot, they know everything visible in the frame rather than everything you meant to show, which is the recurring problem with screenshots and is set out in screenshots and photos.

A technically-minded friend learns more than a stranger, because they can interpret it. A stranger on a forum sees an error message. A friend sees an error message and already knows where you live, what your week looks like and what you were probably doing. The same disclosure lands differently depending on how much context the receiver already has.

What a public question leaves behind that a private one does not

A private question to one person is a conversation. It has the properties of every other conversation in this section: a memory, possibly a message in two accounts, and a count that went from one to two.

A public question is an artifact. It has a timestamp, an author, a permanent address, and it is searchable by anybody at any time in the future including people who are not looking for you. It attaches to a posting identity, which accumulates a history: this account asked about that, then about the other thing, then mentioned a timezone, then used a phrase it uses everywhere else. Nobody has to be watching for the accumulation to happen, because the archive does it on its own.

It is also frequently copied. Forum content is scraped, mirrored, quoted in other threads, and indexed. Deleting a post removes it from one place. This card makes no claim about how many other places exist, because that is not knowable, which is itself the point.

What a helper does not need

Almost every genuinely sensitive item is diagnostically useless. Your account name is not needed to explain why a page fails to load. The full address is not needed when the shape of the address is the question, and the addresses at the top of this page are not what anybody is asking you for. An order reference tells a helper nothing about a browser problem. A delivery address is never part of a technical answer.

The exception is when the question is genuinely about the specific value rather than about the behaviour, and that is rarer than it feels. Most requests for help are about a mechanism, and mechanisms are describable without identifiers. Saying that a page returns a particular error after a particular action is the whole of the useful content in the large majority of cases.

What changes the answer

6 things change how much this action gives away. None of them takes it to zero, and none of them is a promise.

1. Decide public or private before you start typingThese are different acts with different lifetimes and the decision is easy to make in advance and impossible to reverse afterwards. A private question costs you one more person in the count. A public one costs you a durable record. Neither is automatically the right choice.
2. Crop and check the screenshot before it leaves the machineScreenshots capture the whole frame including the tab bar, the taskbar, the clock, notification banners and any window edge behind the one you meant. Cropping to the error itself, or retyping the error text instead, removes the entire category. It does nothing about the content of the error message itself.
3. Describe the behaviour, not the accountWhat happened, at what step, with what wording, in what browser. That is the diagnostic payload. Identifiers are not part of it and adding them does not make the answer better. This will not work when the question genuinely is about a specific value.
4. Assume a public question is permanentWrite on the basis that the post outlives the problem, the thread, the forum and your interest in it. That is the realistic default rather than a pessimistic one. It does not mean anybody will ever read it.
5. Separate the posting identity from everything elseAn account used to ask questions accumulates a history that is readable as a whole rather than post by post. Keeping that history from joining up with anything else is the difference between one question and a profile. It requires care over a long period and one lapse undoes a lot of it.
6. Ask the narrowest version of the questionMost problems reduce to a general question that has nothing to do with your situation: what does this error mean, why does this setting behave this way. The general version is answerable by more people and discloses nothing. Sometimes the general version is not the question you have.

What this card is not

This card is not against asking for help, which is often the correct and sensible thing to do. It is about which parts of the question are doing diagnostic work.

Questions that come up

Is a private message to one person safe?

It is smaller, not safe. It has the same arithmetic as telling one person, plus a written record in two accounts that may sync or be backed up. Smaller is a real improvement and it is not the same as nothing.

Should I delete a post once the problem is solved?

Deleting removes it from the place you deleted it. Whether copies exist elsewhere is not something this site can tell you, and any answer claiming otherwise would be inventing certainty.

Does a helper need to know which market it is?

For most technical questions, no. Browser behaviour, connection failures and interface confusion are usually generic. When the question is genuinely about one site's behaviour, the name of the site is doing real diagnostic work and leaving it out just wastes the helper's time.