This might be a collision with markdown support in chat, but it gets very annoying when you want to post images from e.g. ebay as they almost always contain the dollar sign, e.g.


When you post that in chat, the outcome is:


which is unexpected as well as unusable.

  • Some Wolfram Alpha links look bad too: wolframalpha.com/input/?i=BodePlot[+ReplaceAll+[1/…^2+%2B+s(R_1+C_1%2BR_1+C_2%2BR_2+C_2)%2B1),+{C_1+-%3E+0.001,+R_1+-%3E+100,+C_2+-%3E+0.000001,+R_2+-%3E+100}+]+] Nov 11, 2015 at 19:58
  • It looks to me like those get cut at "^" instead. wolframalpha.com/input/?i=1%2Fs%5E2 works though. I suspect the problem might be that the web standards dictate these symbols to be %-encoded. But some browsers don't always do that. Nov 11, 2015 at 19:59
  • @RespawnedFluff: does ^ have a meaning in markdown? If not, then the markdown collision theory is moot
    – PlasmaHH
    Nov 11, 2015 at 20:01
  • Could you instead upload the image to Stack Exchange's server first?
    – user213963
    Nov 11, 2015 at 20:47
  • @MichaelT: I am sure we can find lots of annoying workarounds for all cases where this fails, but whats the point then? Is there a good reason for the URIs to not work properly and people are forced to better always either scan the complete URI manually or feed it through some other mechanism?
    – PlasmaHH
    Nov 11, 2015 at 20:51
  • 1
    This is an issue of the link parser and one boxer on the chat server. If you aren't one boxing, its always nice to wrap it in a nice []() link for people reading chat. If you are one boxing, its nice to put it on stack exchange's server for places that do things like block ebay at work.
    – user213963
    Nov 11, 2015 at 20:53
  • @MichaelT: I dont know what this boxing is you and the duplicate talk about but well, if its too much to ask for stackexchange to work like every other chat you know and just make links into clickable entities then thats probably a feature
    – PlasmaHH
    Nov 11, 2015 at 21:07
  • @PlasmaHH one boxing is when the chat engine takes the link and puts it in a chat box. Like a post to a SE question, comment, amazon, wikipedia, xkcd, youtube, ... or an image. It does make links into clickable things, but it tries to be smarter about it.
    – user213963
    Nov 11, 2015 at 21:11
  • @MichaelT: It seems a different parser is used for bare URLs vs [](). Because the Wolfram Alpha example also works with the latter. And not only in chat but also here in comments. Nov 11, 2015 at 21:16
  • @RespawnedFluff yep. The []() parser is one that works with the chat subset of markdown rather than trying to work with the chat oneboxing feature. Personally, if I can, I like wrapping all links in []() so that the link is more meaningful to other people reading it.
    – user213963
    Nov 11, 2015 at 21:18

1 Answer 1


Yeah, looks like the chat wants it to be escaped. Until it's fixed, the workaround is to replace the dollar sign in your link with $, so as to get:



  • 2
    Having to manually fix the URI to be usable in chat is pretty useless, especially with automatically generated URIs and as RespawnedFluff said, it seems to be the case with ^ too. And what other char? It isn't really useful to memorize a list with all the chars and manually replace them, especially not if you are not an everyday chat user ...
    – PlasmaHH
    Nov 11, 2015 at 20:03
  • @PlasmaHH Completely agree, this answer is a workaround until it's fixed :)
    – nicael
    Nov 11, 2015 at 20:04
  • Btw, the useful list of html entities, do you think I memorize them? :D
    – nicael
    Nov 11, 2015 at 20:05
  • looks like its by design and they consider all browsers broken sigh
    – PlasmaHH
    Nov 11, 2015 at 20:18

Not the answer you're looking for? Browse other questions tagged .