lmao the problem is that it's our own function that's doing this, we rely on browser's URL detection to do our checks but maybe we shouldn't rely on it that much.

Great!

Solution: make your own function to check for valid links! ~lol

0xbitcoiner

gh issue: https://github.com/stackernews/stacker.news/issues/2889

Okay I think I got what's happening here, the clue is:

but if I swap the '.' for ',' the error doesn’t happen anymore.

We check for misleading links, stuff like 

 and we replace the 'misleading' link with 

But the way we check for misleading links seems to differ between browsers. For Safari, 

 is of course not a domain and not even a URL; for Chromium 

 is instead a perfectly valid URL and will trigger the misleading link replacement.

econ

Measuring Poverty Correctly Reveals a Hard Truth About the Welfare State

Okay I think I got what's happening here, the clue is:

> but if I swap the '.' for ',' the error doesn’t happen anymore.

We check for misleading links, stuff like `[google.com](bing.com)` and we replace the 'misleading' link with `[bing.com](bing.com)`. You know, to keep it fair.

But the way we check for misleading links seems to differ between browsers. For Safari, `https://11.1 percent` is of course not a domain and not even a URL; for Chromium `https://11.1 percent` is instead a perfectly valid URL and will trigger the misleading link replacement.

We need to make the check more clever.