So if its just a URL without the []() syntax it would be, perhaps green, and links with it could stay blue. Good semantic to avoid spam or malware links.
Anyway, have any of you seen today’s XKCD? https://xkcd.com/3104
So if its just a URL without the []() syntax it would be, perhaps green, and links with it could stay blue. Good semantic to avoid spam or malware links.
Anyway, have any of you seen today’s XKCD? https://xkcd.com/3104
^https?://[a-zA-Z0-9\.-]+(/[^\s]*)?$Been a while since I’ve written regex and it could certainly be a little bit more correct. But whatever Voyager already uses to find URLs in a text to turn into a link should suffice.
Okay, now what if I put in an invisible Unicode character in there?
For that you strip the string to be tested of all non-ASCII chars before you run the regex.
But I see what you mean. I just fear that if links could be shown in different equally non-threatening colors users wouldn’t know what to do with that information.
Okay, what if I use unicode characters that look similar to httрѕ://хkсd.соm/ and the function sees that an empty string is not a URL.
Yeah, I think the link preview is the only real solution. Like you said, best shown under the same paragraph.