i think microsoft started the trend of link-ifying URLs in outlook text emails reader and excluding .,)]

after that started, every PM/exec just want it to work like it works everywhere-else. Everywhere-else being their corporate email client, and then it comes full circle and indeed does work like that everywhere.

HN's primitive URL parsing definitely doesn't derive from Microsoft :)

I did some work on it last year to take care of the worst omissions, and angle brackets should also now work to demark tricky URLs but there are still some edge cases. For example, <https://en.wikipedia.org/wiki/Doe_v._Exxon_Mobil_Corp.> should work, but doesn't (yet!)

Edit: now it does. So should these:

<https://en.wikipedia.org/wiki/Sagittarius_A*>

<https://en.wikipedia.org/wiki/Jack_Weinberg#"Don't_trust_any...>

<https://en.wikipedia.org/wiki/Great_Northern_Railway_(U.S.)>

<https://developer.android.com/reference/android/location/Loc...>

They are all cases of URLs that don't get picked up correctly by HN's current parser. At least now they work with angle brackets.

Let’s see if this works: https://en.wikipedia.org/wiki/Doe_v._Exxon_Mobil_Corp%2E

Yes! You can work around the issue by encoding the trailing dot as %2E.

And in Outlook you can enclose URLs in <…> delimiters.