# Configuring X login and rich embeds for Discourse

**URL:** https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395
**Category:** Integrations
**Tags:** sso, how-to, social-auth
**Created:** [3월 4, 2014, 6:03오후 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395 "2014-03-04T18:03:12Z")
**Posts on this page:** 1
**Showing post:** 165

<div class="post-metadata">

### Author: ![Jonathan5](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jonathan5/32/197134_2.png) [@Jonathan5](https://meta.discourse.org/u/Jonathan5)
#### Post date: [4월 14, 2023, 11:07오후 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/165 "2023-04-14T23:07:40Z")

</div>

> [@Kartoon](#):
>
> 여전히 리치 임베드를 사용할 수 있나요?

이론적으로는 가능한 것 같습니다:

> [@임베드된 트윗 미리보기, 이제 안녕](https://meta.discourse.org/t/bye-bye-embedded-tweet-previews/261708/12?u=jonathan5):
>
> Where does this fit into the grand scheme of things? The oEmbed API returns simple embed HTML in an [oEmbed](http://oembed.com/)-compatible format. You can use the oEmbed API to programmatically return embedded content, such as [Tweets](https://developer-staging.twitter.com/en/docs/twitter-for-websites/embedded-tweets/overview) and [timelines](https://developer-staging.twitter.com/en/docs/twitter-for-websites/timelines/overview). The response from the oEmbed API will return an HTML snippet that will be automatically recognized when [Twitter’s widget JavaScript is included on the page](https://developer.twitter.com/web/javascript/loading). Please note that the API is recommended for performing tasks in bulk, and we advise using our robust [publish.tw…](https://publish.twitter.com/#)

하지만 Discourse가 해당 API를 사용하지 않는다고 생각합니다.

---

_[View the full topic](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395)._