MWB won't linkify a bare http/https link, like https://example.com/, but it will if you put angle brackets around it, like <https://example.com/>.
As a fan of RFC 1738, I actually kind of like this, even though I think most people would just want it linkified without the angle brackets. Maybe some day when we get a round tuit.
In addition, there are many occasions when URLs are included in other kinds of text; examples include electronic mail, USENET news messages, or printed on paper. In such cases, it is convenient to have a separate syntactic wrapper that delimits the URL and separates it from the rest of the text, and in particular from punctuation marks that might be mistaken for part of the URL. For this purpose, is recommended that angle brackets ("<" and ">"), along with the prefix "URL:", be used to delimit the boundaries of the URL. This wrapper does not form part of the URL and should not be used in contexts in which delimiters are already specified.
MWB won't linkify a bare http/https link, like
https://example.com/, but it will if you put angle brackets around it, like<https://example.com/>.As a fan of RFC 1738, I actually kind of like this, even though I think most people would just want it linkified without the angle brackets. Maybe some day when we get a round tuit.
From {RFC 1738](https://datatracker.ietf.org/doc/html/rfc1738):