Solved Using unfurl in a URL

  1. [URL unfurl="true"]https://www.freebsd.org/releases/[/URL]
  2. [URL unfurl="true"]https://forums.freebsd.org/threads/formatting-guidelines.49535/[/URL]
  3. [URL unfurl="true"]https://forums.freebsd.org/threads/for-all-the-people-using-freebsd-as-their-primary-desktop.84983/post-565162/[/URL]
Why does "unfurl" work in #1 & #2 but not in #3?
As shown in:

Or am I missing something?
 
Thanks, I think there is some kind of a delay at work. When preparing my message I didn't see the link "unfold"; even after posting and trying several times thereafter it stayed the same. Also tried another browser: still unfolded.

Now I can see #3 unfolded; but, at this moment, I still don't see the unfurl unfolded in my other message: this one
 
I found a guy having the same problem and he says he needed to remove the url-tag for unfurling:

 
Yes, that helped. I'm still not sure what exactly prohibits it and what makes it switch on. However, what counts is that others seem to see it, always. Fiddling with removing and then adding the [url]-tags, sometimes with clicking on "Preview", seems to do the trick.

My suspicion is that is has something to do with the (auto)fetching of the content (from the specified url) that is shown in the unfolded link and with browser caching (the latter has the tendenacy to behave in unexpected ways when you least expect it ... ).
 
As far as I understood the function the actual "unfurling" happens on the client, it's not done server-side. It's your local browser that fetches and renders that preview.
 
Back
Top