# Onebox Twitter embedding

**URL:** https://meta.discourse.org/t/onebox-twitter-embedding/18943
**Category:** Feature
**Created:** [August 17, 2014, 10:16am UTC](https://meta.discourse.org/t/onebox-twitter-embedding/18943 "2014-08-17T10:16:41Z")
**Posts on this page:** 1
**Showing post:** 56

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [October 5, 2020, 7:20am UTC](https://meta.discourse.org/t/onebox-twitter-embedding/18943/56 "2020-10-05T07:20:42Z")

</div>

You might want to look at:

> [@Discourse does not produce large, more engaging Twitter cards](https://meta.discourse.org/t/discourse-does-not-produce-large-more-engaging-twitter-cards/165479/4):
>
> Is there any way to overwrite the behavior of def crawlable\_meta\_data with a simple plugin? In particular, we would like to change: elsif opts[:image].present? result \<\< tag(:meta, name: 'twitter:card', content: "summary") result \<\< tag(:meta, name: "twitter:image", content: opts[:image]) to elsif opts[:image].present? result \<\< tag(:meta, name: 'twitter:card', content: "summary\_large\_image") result \<\< tag(:meta, name: "twitter:image", content: opts[:image]) as we’re…

---

_[View the full topic](https://meta.discourse.org/t/onebox-twitter-embedding/18943)._