The original topic & issue was this:
Some time ago Discourse stopped displaying the Twitter links properly as previews. I now only get an error message.
It seems to work for you guys. Why ever!
I am using the latest version. What could be the problem?
Example at meta:
On my instance:
[image]
Today I received the following email from Twitter:
Application suspension notice
Hello,
Please visit developer.twitter.com to sign up to our new Free, Basic or Enterprise access tiers.
More information can be found on our developer community forums.
Regards,
Does anyone know what this is about?
+++ Update +++
https://twitter.com/hashtag/ApplicationSuspensionNotice?src=hashtag_click
Rules and Policies
Rules and Policies
I’ve just received this alarmingly worded email. From: Twitter support@twitter.com Subject: Application suspension notice Date: April 10, 2023 at 16:41:58 MST Hello, This is a notice that your app - [APP NAME HERE] - has been suspended from...
Reading time: 5 mins 🕑
Likes: 34 ❤
Hopefully at some point the Discourse developer team can come up with a sustainable solution to the Twitter problem so that a Twitter App & API is no longer necessary for every single forum owner.
1 Like
I think the idea is to charge people for accessing Twitter data via the API, but it seems that the oEmbed API allows embedding (using the URL of an existing tweet) at no cost:
Where does this fit into the grand scheme of things?
The oEmbed API returns simple embed HTML in an oEmbed -compatible format. You can use the oEmbed API to programmatically return embedded content, such as Tweets and timelines .
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 .
Please note that the API is recommended for performing tasks in bulk, and we advise using our robust publish.tw…
2 Likes
There is some discussion about this in the topic @Jonathan5 has linked so I’ll close this one off so we can focus the conversation there.
1 Like
