alt Hacker NewsMy most blood boiling error message (long time ago, maybe they fixed it):
"No headset audio" -- displayed by the Oculus desktop app, in regards to not having audio on the headset. There's a "learn more" link, which would send you to the general troubleshooting FAQ.
So, the program knows something is wrong with the audio, but completely refuses to say what. Is it a headset problem, a driver problem, a restart needed!?
Then to make it more fun, when I complained about this stuff originally I got the advice to upload a debug log. Ok, good. That failed every time with "The upload took too long, connection was lost". I pulled out the dev tools and then I saw that what the API actually returns is:
[{"error":"Attachment is too large. Limit 20 megabytes."}]
Replies
> My most blood boiling error message (long time ago, maybe they fixed it):
I still have a screenshot from a long time ago from a Microsoft product and the error message reads something like that:
"Possible causes: xxx, yyy, your computer may be off".
That one is so dumb I took a screenshot back in the days and still have it somewhere in my backups.
What they meant was "the computer you're trying to contact may be off", not "your computer may be off". I honestly think that one takes the icing on the cake.
But I've got another contender screenshot, still from a Microsoft product, saying something like this: "We suggest you write the following password down: z_7-9$HqR2_vM5$pL8-wN1_bX4$kZ7-jT0_yC3$fS6-uG9_aD2$hI5-rP8_eQ1$mW4E8_oQ1$tV4-6_x$K9_j-2$G5_s-8$W1_b-4$N7_m-0$Z" [1]
This was pre-ubiquitous QR code days.
[1] and, yes, it was so dumb I preferred to take a screenshot of the password than be "secure", so I could make fun of that message forever. And I gotta say, that screenshot did age like fine wine.
Atlassian of all people did this right - you can upload a support zip and it warns if it’s large (do you want to try?) and gives you the option of (basically) the last 10/20 MB of logs to send instead.