Choose between a Free, Basic, or Pro X Dev plan and complete the developer agreement and policy requirements. If you would like to have rich embeds on your forum you’ll need at least a Basic plan for X Dev. Rich embeds will not work with the Free X Dev plan.
After completing the agreement and policy requirements you’ll be taken to the X dev dashboard where a default project and app will be created.
Update your default Project and App
Under your default project title, click the Settings tab followed by the Edit button.
Edit the project name, use, and description (optional) followed by clicking the Save button. If you are using an account with a Basic or Pro plan please select Embedding_Tweets_in_a_website.
Click the Overview button below the project title and scroll down to the Apps section.
In the Apps section, click the cogwheel icon, or App_Settings, to the right of your app name.
Copy and paste the API Key from X into the twitter_consumer_key setting.
Copy and Paste the API Key Secret from X into the twitter_consumer_secret setting.
Click the green checkmark to save the changes.
Users should now be able to log into your forum using their Twitter Account.
Rich Embeds
The above steps also apply if you want to enable “rich embedding” which allows displaying tweets with their media (images video, etc). If you want rich embeds but don’t need Twitter login, simply uncheck enable twitter logins and leave the consumer key and secret intact.
Rebaking Posts / Rebuild HTML
It’s important to know that rebaking or using the rebuild HTML button on posts that contain tweets will re-pull the tweet(s) and count them towards your monthly tweet cap usage.
Just noticed we were getting the same error on our site with Twitter auth. I noticed Twitter has a new process for authorizing developer apps, so we are going through the approval process. Not sure if it is related, or if this problem has just been in place for a long time now.
I do recommend that those who haven’t applied on developer.twitter.com for their Twitter app, to do so.
For the near future, you can continue to manage existing apps here on apps.twitter.com. However, we will soon retire this site and consolidate all developer tools, API access, and app management within the developer portal at developer.twitter.com. You will be able to access and manage existing apps through that portal when we retire this site.
You are probably using some extension that blocks social media, tracking or something similar. Try logging in from an anonymous window with all extensions disabled
I hope this is the right place to ask this question. I see from https://try.discourse.org/ that registration by Twitter leads to the following message:
This application will be able to:
See Tweets from your timeline (including protected Tweets) as well as your Lists and collections.
See your Twitter profile information and account settings.
See accounts you follow, mute, and block.
See your email address.
Is it possible to set it up where it sees the minimum amount of information necessary - name and email address I think?
This is already the minimum information required by Twitter.
As you can see from the guide, the only thing we require from Twitter is the user email that Discourse needs to create the user account. Everything else is the basic settings decided by Twitter selecting “Read only” in the App Permission section.
I don’t use Twitter, but I assume the reply link is different from the original tweet’s link. Therefore, you are only linking to the reply. Does linking to the original tweet also include the first reply or just the original tweet?
No the idea is that if you embed the reply you can choose to have the original tweet above it as in the pic. So the reply has context.
I quite like the styling too.
I’m just getting the reply.
A workaround is two embeds.
That is indeed a work-around. But how can you choose to have the original tweet above a reply? So how would one “choose”? I do see at times someone posts on another website that the original tweet has the first reply to it.
I am noticing the same registration issue as well. When I try using a test account, and Twitter even states at register that email is being accessed, the email account is not prefilled into the account registration form after completing the authentication handshake with Twitter, and it is also showing “user_1” for the prefilled username. Rich embeds are not working as well.
In order for rich embeds to work properly a Basic plan for X Dev is mandatory. Rich embeds will not work with the Free X Dev plan.
