CBD: ...because HuffPo coded their page to prevent cutting and pasting...

There's always a workaround.

Seamus Muldoon #160: ...Mis Hum inadvertently prepended part of the AOSHQ address in front of the link URL....

Kafiroon was just enhancing the art post by demonstrating effective use of white space.

Anachronda "I thought the ampersands might prove tricksy."

Gem: "I copied and pasted from the post and Pixy no like it"

Commenters who don't want 500 errors (and AHEM! post bloggers who don't like black diamonds):

SarahW, you can use those Unicode characters on here (maybe) if you pre-wash your message here:
http://bit.ly/pixyize

“…no idea what you’re talking about.”

andycanuck: That's weird. Aren't those supposed to start with instead of #? I usually don't do the number bits, but use things like hellip; ( … ).

Computing: It's not for the timid. You say, "It took me a long time and a lot of trial and error to learn how to post graphics in the reply section." No kidding.

Is there something maybe missing in the post lead? I notice it seems to begin with a stray less-than/html tag opener.

Asking for an obsessive-compulsive friend.

I know, this post looks like a Monty Doom article.
http://tinyurl.com/nt25gej
Posted by: Vic

Only, bolder.

Okay, don’t know if you’ll see this addition to more-than-week-old thread but I just found it.

♥

If that works, it’s done thusly: ♥

Chrissyyyyyyyy! Like your graphics, BUT... (don't you hate it when someone starts that way?)

My trepidation was simply that I wouldn't want to be muddying this lovely crystal pool when things are going so swimmingly. (Block that metaphor!)