Article 63Q1F Error'd: Taking the Piss

Error'd: Taking the Piss

by
Lyle Seaman
from The Daily WTF on (#63Q1F)

In case anyone is wondering "is there anything so lame that it's not evengood enough to get published by Error'd", the answer is yes. There is acategory of submissions that is very common, but in the completely capricious opinion of this editor, just not very funny. That category is clearly broken listings on amazon.com. We usually get two or three of theseevery week. We save them up, and maybe someday the news will be so slow that we have no choice but to run an entire column of nothing but Amazon bloopers. This week was no different from the usual, except that this timethe September stress has struck a nerve and so you get to see what the brink of madness looks like from the inside.

Tippler Matthias poured one out for us. "Seems someone already tried some of the good stuff while uploading the images to Amazons catalog."

04-dewars.png

Toddler Rob H. tee-hee'd "From ServiceNow's attempt to truncate the Description field(customer e-mail body) to a small space... the wish, ofcourse, was for a nice weekend. Who knew it would leadto a bit of Monday morning toilet humor?"

02-wee.png

Number-crosser Drew W. has a first with this."I don't know how, but either Apple Numbers or MicrosoftExcel has made font typos into a thing. (It's Calibri, not Calirbi)"

01-calibri.png

CinephileMike T. ad-libbed dramatically "I was just trying to browse a local theatre's websitewhen this error message barfed up on my screen, apparently due to Facebook ... something."

03-facebook.png

Quoth Apple-sauced Carl C. in confusion"I can only surmise that this product works so well that it blocked its own ad?"

05-mac.jpeg

buildmaster-icon.png [Advertisement] Utilize BuildMaster to release your software with confidence, at the pace your business demands. Download today!
External Content
Source RSS or Atom Feed
Feed Location http://syndication.thedailywtf.com/TheDailyWtf
Feed Title The Daily WTF
Feed Link http://thedailywtf.com/
Reply 0 comments