So I posted a link to
https ://www.msn.com/en-us/news/us/he-voted-for-trump-now-his-wife-sits-in-an-ice-detention-center/ar-AA1B0Qwo
[note an extra space added to show what is happening]
And the link was instead posted as
https ://www.msn.com/
What is the problem and the fix?
Testing this:
Worked okay for me from Edge. Doesn’t show a preview, but the full title of the link is correct.
He voted for Trump. Now his wife sits in an ICE detention center.
But from Chrome:
Maybe a Microsoft thing?
And indeed, the edit window still shows the full link, but the box truncates it.
Looking at it again: the end
ar-AA1B0Qwo
Is that a referral that Straightdope doesn’t like?
I wonder if that has something to do with the article not being their original article, but a actually from USA Today. It works when the original article is posted. Could there be some sort of hotlinking going on that’s confusing discourse?
The article doesn’t work at all if you delete that part. And, even the share button, within the article, doesn’t work.
Seems to be either a bug in the OneBox system or in the way the page presents the data. A bare link works fine:
He voted for Trump. Now his wife sits in an ICE detention center
But when you use the OneBox feature, Discourse pulls some information from the page and uses that. I suspected it was the way the page advertises the canonical URL, but as best I can tell that’s not the case. Here’s the HTML from the page:
<meta property="og:url" content="https://www.msn.com/en-us/news/us/he-voted-for-trump-now-his-wife-sits-in-an-ice-detention-center/ar-AA1B0Qwo">
Fairly sure that it’s the og:url property that Discourse uses. And that looks fine. So I’m not sure right now.
I use Firefox. So it worked OK using Edge, but didn’t work correctly with Chrome and Firefox.
Weird.
The work-around is to put at “<” at the beginning of the link and a “>” at the end of the link.