# 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:** [4 maart 2014 om 18: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:** 20
**Page:** 3

<div class="post-metadata">

### Author: ![wineberserkers](https://avatars.discourse-cdn.com/v4/letter/w/96bed5/32.png) [@wineberserkers](https://meta.discourse.org/u/wineberserkers)
#### Post date: [19 augustus 2022 om 19:43 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/120 "2022-08-19T19:43:39Z")

</div>

Finally ‘fixed’ the site (migrated from phpbb Tuesday) and got embed to work, but the size is crazy - anyone know the fix for that?

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/8/4/88429024956a58068b11e79728f01f9976869588.jpeg)

---

<div class="post-metadata">

### Author: ![riteshsaini](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riteshsaini/32/266453_2.png) [@riteshsaini](https://meta.discourse.org/u/riteshsaini)
#### Post date: [26 augustus 2022 om 11:21 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/121 "2022-08-26T11:21:58Z")

</div>

They have recently added Environment setting.

My app is set to Development. There are two other options: Production and Staging.

Should I change to either of the two?

---

<div class="post-metadata">

### Author: ![Kartoon](https://avatars.discourse-cdn.com/v4/letter/k/e36b37/32.png) [@Kartoon](https://meta.discourse.org/u/Kartoon)
#### Post date: [1 oktober 2022 om 15:54 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/122 "2022-10-01T15:54:08Z")

</div>

Edit: Used the wrong keys lol fixed it

Is there a way to rebuild posts that have Twitter links before the API was set up? Not a huge deal if there’s no way to retroactively embed them but would be cool

---

<div class="post-metadata">

### Author: ![danielabc](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@danielabc](https://meta.discourse.org/u/danielabc)
#### Post date: [12 oktober 2022 om 09:28 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/123 "2022-10-12T09:28:39Z")

</div>

how you fix it? my link are broken

---

<div class="post-metadata">

### Author: ![danielabc](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@danielabc](https://meta.discourse.org/u/danielabc)
#### Post date: [26 november 2022 om 17:38 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/124 "2022-11-26T17:38:48Z")

</div>

> [@Hifihedgehog](#):
>
> tá acontecendo, no entanto. Do jeito que está, porém,

I can’t get approved, what did you do to get it so fast?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [28 november 2022 om 10:08 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/125 "2022-11-28T10:08:45Z")

</div>

I assume approvals are going to be very very slow for the foreseeable future, there was a massive staff reduction at twitter recently

---

<div class="post-metadata">

### Author: ![danielabc](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@danielabc](https://meta.discourse.org/u/danielabc)
#### Post date: [28 november 2022 om 19:05 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/126 "2022-11-28T19:05:50Z")

</div>

Do you know why posts embedded by twitter appear like this?

 ![image](https://global.discourse-cdn.com/meta/original/4X/6/f/5/6f5990f8863685127d4d46bc3efcb64010b57bbc.png)

---

<div class="post-metadata">

### Author: ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo)
#### Post date: [3 december 2022 om 22:47 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/127 "2022-12-03T22:47:19Z")

</div>

The upgrading (for free) the twitter dev account to the **Elevated** tier is crucial to get this to work - Please include in the OP for future discoursers. Thanks. 👍

---

<div class="post-metadata">

### Author: ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo)
#### Post date: [4 december 2022 om 14:30 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/128 "2022-12-04T14:30:06Z")

</div>

What’s the deal with 500 error when posting a topic with one or more twitter embeds?

Sometimes occurs when posting or when editing OP post or maybe another post with twitter links.

I’ve also seen discourse serve the **“Oops…”** white page message of text post implementation of above twitter API’s guide, though it works, it’s buggy.

Maybe something in configuration side or DNS/Cloudflare needs to be additionally tweaked?

---

<div class="post-metadata">

### Author: ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo)
#### Post date: [5 december 2022 om 21:50 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/129 "2022-12-05T21:50:26Z")

</div>

I’m not seeing this issue since running an update a few hours after this post, it was pretty close to latest with only about 36 commits new.

---

<div class="post-metadata">

### Author: ![xebiyen](https://avatars.discourse-cdn.com/v4/letter/x/858c86/32.png) [@xebiyen](https://meta.discourse.org/u/xebiyen)
#### Post date: [21 januari 2023 om 08:52 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/131 "2023-01-21T08:52:12Z")

</div>

What is OP? i dont understand

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [21 januari 2023 om 09:39 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/132 "2023-01-21T09:39:27Z")

</div>

> [@xebiyen](#):
>
> OP

Original post. So the first post of the topic is meant. You can also see that the first post was edited and the information was added

---

<div class="post-metadata">

### Author: ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)
#### Post date: [21 januari 2023 om 15:20 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/133 "2023-01-21T15:20:24Z")

</div>

Followed the guide and have an elevated account on the twitter apis.

Links to twitter still appears without preview.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [21 januari 2023 om 16:01 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/134 "2023-01-21T16:01:28Z")

</div>

Have you tried making an API call from the terminal on the machine in question?

---

<div class="post-metadata">

### Author: ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)
#### Post date: [21 januari 2023 om 17:55 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/135 "2023-01-21T17:55:49Z")

</div>

No, can you point me to a guide of how to test it?

---

<div class="post-metadata">

### Author: ![hiddenseal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiddenseal/32/284273_2.png) [@hiddenseal](https://meta.discourse.org/u/hiddenseal)
#### Post date: [30 januari 2023 om 17:39 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/136 "2023-01-30T17:39:13Z")

</div>

Did anyone have an issue with getting elevated access? Described my use cases with links to website and this topic, but got rejected.

---

<div class="post-metadata">

### Author: ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)
#### Post date: [2 februari 2023 om 13:23 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/139 "2023-02-02T13:23:57Z")

</div>

Twitter is going to change access to the APIs starting the 9th of this month.

Maybe we should reflect that in the guide so that it’s clear that this will need to use a paid feature of twitter.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2 februari 2023 om 17:56 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/140 "2023-02-02T17:56:31Z")

</div>

It’s been updated.

Here’s a story about it. I’ll be surprised if they manage to make it work by then. It sounds like they don’t even know what they intend to do.

> **[Twitter is replacing free access to its API with a new paid tier](https://www.theverge.com/2023/2/2/23582615/twitter-removing-free-api-developer-apps-price-announcement)**
>
> Pricing has not been disclosed but more details should arrive next week

EDIT: Oh. I this might be considered off-topic; I didn’t (completely) mean to make this about whether one might ever want to use twitter. Maybe don’t reply along the lines of “Twitter might not be a good idea” and only with stuff like “I tried it and it {did not work|worked}” 🙂

---

<div class="post-metadata">

### Author: ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)
#### Post date: [2 februari 2023 om 20:08 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/141 "2023-02-02T20:08:23Z")

</div>

> [@pfaffman](#):
>
> It sounds like they don’t even know what they intend to do.

Color me surprised 😛

---

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [3 februari 2023 om 19:25 UTC](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395/142 "2023-02-03T19:25:24Z")

</div>

> [@Crius](#):
>
> Maybe we should reflect that in the guide so that it’s clear that this will need to use a paid feature of twitter.

I actually re-wrote (currently as a draft) the whole tutorial two days before Twitter’s announcement … 😭

There are still parts to clean up and refine, but since Twitter is going to change its plans, it’s on hold until we know more about it. 🤞  
If we’re lucky, my re-writing will still be relevant!

[Previous page](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395.md?page=2)

[Next page](https://meta.discourse.org/t/configuring-x-login-and-rich-embeds-for-discourse/13395.md?page=4)
