# Post previews in Telegram

**URL:** https://meta.discourse.org/t/post-previews-in-telegram/306970
**Category:** Bug
**Created:** [May 6, 2024, 6:32pm UTC](https://meta.discourse.org/t/post-previews-in-telegram/306970 "2024-05-06T18:32:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![MarcP](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcp/32/160184_2.png) [@MarcP](https://meta.discourse.org/u/MarcP)
#### Post date: [May 6, 2024, 6:32pm UTC](https://meta.discourse.org/t/post-previews-in-telegram/306970/1 "2024-05-06T18:32:09Z")

</div>

I noticed the previews in Telegram for post-links do not get the actual post preview.

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/4/6/9466621d75258710cb30487bd9564ea6471fd68e.jpeg)

Actual post link:

> [@Preparing for Discourse's upgrade to Ember 5](https://meta.discourse.org/t/preparing-for-discourses-upgrade-to-ember-5/287211/61):
>
> Performance improvements are something we’re constantly investing in, so I don’t think there will ever be a date when it’ll be “done”. In terms of the metrics you shared, it’s important to note that those reflect only the first visit to the community. Clicking around the site, and coming back in future, will be significantly faster!

Some related SO:

> <https://stackoverflow.com/questions/55633306/update-telegram-link-preview-programmatically>

> <https://stackoverflow.com/questions/35268940/how-to-force-telegram-to-update-the-link-preview>

For example, I can randomly /?v=3333 to my link, and can see that Telegram fetches new metadata for the URL, but in case of a specific post, the same is shown, makes me wonder if the issue is on Discourse side?

---

<div class="post-metadata">

### Author: ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [May 6, 2024, 8:02pm UTC](https://meta.discourse.org/t/post-previews-in-telegram/306970/2 "2024-05-06T20:02:01Z")

</div>

I’m not sure this is Discourse-specific, I tested the URL above in a) a different Discourse instance and b) an Open Graph tester like opengraph.xyz, and both show the correct excerpt.

---

<div class="post-metadata">

### Author: ![MarcP](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcp/32/160184_2.png) [@MarcP](https://meta.discourse.org/u/MarcP)
#### Post date: [May 6, 2024, 8:04pm UTC](https://meta.discourse.org/t/post-previews-in-telegram/306970/3 "2024-05-06T20:04:41Z")

</div>

Perhaps Telegram is doing something different.. the issue is not happening in Discord as well.

---

<div class="post-metadata">

### Author: ![MarcP](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcp/32/160184_2.png) [@MarcP](https://meta.discourse.org/u/MarcP)
#### Post date: [May 6, 2024, 8:53pm UTC](https://meta.discourse.org/t/post-previews-in-telegram/306970/4 "2024-05-06T20:53:14Z")

</div>

This is what Telegram is looking at:

```plaintext
<link rel="canonical" href="https://meta.discourse.org/t/preparing-for-discourses-upgrade-to-ember-5/287211?page=3" />

```

Which links to: [Preparing for Discourse's upgrade to Ember 5 - #48 by david](https://meta.discourse.org/t/preparing-for-discourses-upgrade-to-ember-5/287211/48)

This is matching with the content Telegram is fetching as seen in my screenshots 🤔

EDIT - this post from 2022 seems related.

> [@Change canonical link-tag for posts Ember-url to use new canonical url](https://meta.discourse.org/t/change-canonical-link-tag-for-posts-ember-url-to-use-new-canonical-url/221480/1):
>
> In crawler-view check the canonical link-tag for a posts Ember-url like:  
> `https://meta.discourse.org/t/feedback-on-new-hamburger-and-user-menus/32519/123`
> 
> ```plaintext
> <link rel="canonical" href="https://DOMAIN/t/SLUG/32519?page=6">
> 
> ```
> 
> This should be changed to contain `…#post_123`:
> 
> ```plaintext
> <link rel="canonical" href="https://DOMAIN/t/SLUG/32519?page=6#post_123">
> 
> ```
