4 ms·

I do, and I wouldn't be surprised if more people here do so as well. Then again, I also wouldn't be surprised at people here not doing so and expecting URL clas

I do, and I wouldn't be surprised if more people here do so as well. Then again, I also wouldn't be surprised at people here not doing so and expecting URL classifier to strip trailing punctuation even though the spec allows it.

JadeNB 6y ago
I also do it, because sometimes the parser does the 'right' think and sometimes it doesn't, and it's easier just never to rely on it. It's tough to fight when the parser thinks it's doing the right thing but isn't; for example, I literally couldn't find out how to send someone a link to https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_Us https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_U...! in Slack; the trailing ! is part of the URL, but Slack resolutely refused to recognise at such. (I don't know what HN's parser does, so I guess we can regard this as an experiment! EDIT: HN also refuses to recognise it. I tried the <> wrapper suggested elsethread, with amusing results: it makes HN's parser gobble both the ! and the trailing > as part of the URL! Maybe a percent-encoding would have been the way to go.)
- deleted 6y ago
  [deleted]
- bmn__ 6y ago
  > I literally couldn't find out how to send someone a link The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`. https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_Us%21 https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_U... > HN also refuses to recognise it. The HN software is RFC ignorant. Could you please send an email to the Web master so the bug can get fixed?
  - JadeNB 6y ago
    > The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`. Yeah, that was my speculation: > > Maybe a percent-encoding would have been the way to go. > The HN software is RFC ignorant. Could you please send an email to the Web master so the bug can get fixed? I try to be conscientious in general about reporting bugs I find in software, but arguing about the details of Markdown parsers is an endless full-time job with no reward. Of course you are welcome to do it if you think it's worth the time.
    - jwilk 6y ago
      It reported this bug to HN (back in 2016…), and they acknowledged it.

JadeNB 6y ago

I also do it, because sometimes the parser does the 'right' think and sometimes it doesn't, and it's easier just never to rely on it. It's tough to fight when the parser thinks it's doing the right thing but isn't; for example, I literally couldn't find out how to send someone a link to https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_Us https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_U...! in Slack; the trailing ! is part of the URL, but Slack resolutely refused to recognise at such. (I don't know what HN's parser does, so I guess we can regard this as an experiment! EDIT: HN also refuses to recognise it. I tried the <> wrapper suggested elsethread, with amusing results: it makes HN's parser gobble both the ! and the trailing > as part of the URL! Maybe a percent-encoding would have been the way to go.)

deleted 6y ago
[deleted]
bmn__ 6y ago
> I literally couldn't find out how to send someone a link The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`. https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_Us%21 https://en.wikipedia.org/wiki/Only_the_Super-Rich_Can_Save_U... > HN also refuses to recognise it. The HN software is RFC ignorant. Could you please send an email to the Web master so the bug can get fixed?
- JadeNB 6y ago
  > The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`. Yeah, that was my speculation: > > Maybe a percent-encoding would have been the way to go. > The HN software is RFC ignorant. Could you please send an email to the Web master so the bug can get fixed? I try to be conscientious in general about reporting bugs I find in software, but arguing about the details of Markdown parsers is an endless full-time job with no reward. Of course you are welcome to do it if you think it's worth the time.
  - jwilk 6y ago
    It reported this bug to HN (back in 2016…), and they acknowledged it.