The discussion addresses the upcoming deprecation of the unauthenticated oEmbed API for Facebook and Instagram, which will require authentication starting October 24th. Users are concerned about the impact on Onebox functionality in Discourse. Terrapop highlights the need for API keys, while rmens notes Instagram embeds are already broken on self-hosted instances. jamie.wilson confirms that updated Discourse instances can use a facebook_app_access_token SiteSetting to maintain Onebox functionality. ljpp provides a step-by-step guide to generate the required token, involving adding the oEmbed product to an app, retrieving the client token, and combining it with the App ID using a pipe character. bartv requests a more detailed guide.
On the 24th of October the unauthenticated oEmbed API from Facebook and Instagram will stop working. They will require authentication to fetch oEmbed objects.
Are there any consequences for Onebox? I couldn’t find any changes in the GitHub repo regarding this yet.
If you’re running an up-to-date Discourse instance you should now be able to add a token that will allow oneboxes to be generated using the new API.
I’ve not yet written up step-by-step instructions on how to generate the token, but if you are comfortable in Facebook’s developer site you can go through the ‘Requirements’ listed here:
And finally combine in a your App ID numbers and the token and ad a pipe | character in between: 12324323|asdasdasdasd ← That is what you need put to the Discourse setting.