Please be aware that your posts here are read by people using email
clients as well as visiting the web site. If you want to put a link
into your posts and you want people to visit it, PLEASE remember to
type a complete URL with the leading protocol. For example:
will be clickable anywhere and everywhere, whereas:
web.mit.edu
will not. Doing this will greatly increase the chances of people
visiting your links. Really.
Sometime around 13/11/08 (at 17:07 -0500) chuckamuck said:
Keith, just an FYI. Both your examples look the same from the web
page, just one is clickable and the other isn’t
Frankly, I wish Walter’s amazing Freewaytalk creation didn’t mask
complete URLs like that. I suspect this is partly to blame for this
problem; people don’t see the difference.
How’s this? This:
http://web.mit.edu/
will be clickable anywhere and everywhere, whereas:
I heartily echo Keith’s point about using complete URLs to make clickable links - see the line above for the correct method. Because this is ‘quoted’ it is not clickable.
This easiest way to achieve this clickable link is to visit the page you want us to see in your browser and copy and paste the full URL from the address bar.
It’s actually a way to avoid an infinite loop! If I left the http:// part on, you would have the classic wine bottle label with a picture of a wine bottle on the label with a picture of a wine bottle on the…
I have been trying to figure out a way to solve this so you would see what you want, but I’m trying to serve two masters here, as you know. On the one hand, if all I had to deal with was the Web form input, then I could use one pass at it with Markdown and be done with it. But since I also accept input from Mail, and have to deal with the thousand ugly things that happen there (don’t get me started about quotable/printable or Base64 or MIME html mail… shudder), I have about fifty lines of regular expressions to deal with that, and it makes it less simple to just throw Markdown at it and be done with things. For the record, regular Markdown happily turns any URL inside of angle-brackets into a link – and leaves the HTTP part still intact.
Hey, what do you know. All that whinging about wine bottles and I fixed it anyway. Code view is still messed up, but everywhere else is fine. I have to figure out a way to keep Markdown from double-encoding the links, and I should be able to fix that part as well.
To be honest…I really don’t mind whether they are clickable or not…even if they are I usually copy them and open them in a new tab…seeing as this forum doesn’t automatically do that - meaning going from link back to the forum takes quite a while to load!
