Well, the auto-linking is getting confused by the multiple periods in the pdf link, and starts reading the following underscores as markdown, which might not be desirable?
But the escape <> wrap is a good workaround if you need it.
It is something that @Vitaly ia tracking, really depends on how common these issues are. If it is 1 in a million links it is not worth improving the linkifier, if it is 1 in 10 it certainly is
It depends. If there is need to share scientific links and pdfs, as on my forum, it is really common covering almost every link. Otherwise, not so often but more than one dot is not so rare form either.
From my point of view — is there some reason why starting http:// or https:// and ending to a space is not enough, plus allowed fileforms of course?
Well, I’m trying to teach users to use < and >. The biggest UX’ish issue here is Discourse starts to act in many cases too differently than users are expecting. But that is much deeper thing than just trying to remember when links work and when not.
I’ve recorded test case but with high probability it’s the same emphasis-based issue as before.
In general, all links with protocol http(s):// can be fixed, and i start working on this very soon (really).
Fuzzy links have no realistic solution (and will open door to ReDoS). But, as i said many times, added value of this mode is not obvious, and it’s disabled by default because of many side effects. I did it only because other packages provided it.