BCHK reports that Twitter oneboxes have stopped working on their Discourse install (v2.9.0.beta9), suspecting it may be related to Twitter changes under Musk. They confirm they’re referring to standard oneboxes, not rich embeds, and show screenshots of the broken behavior. Canapin clarifies that rich embeds are unsupported but suggests checking onebox settings or IP blocking for standard oneboxes. merefield recommends trying the Onebox Assistant crawl tool. RGJ advises updating to the latest Discourse version first, as the issue may already be resolved, and suggests a Twitter Native Embed theme component if updating doesn’t help. merefield agrees, emphasizing that updating before reporting issues is best practice. The consensus leans toward updating Discourse as the first step, followed by checking configs or using alternative tools if needed.
If you are talking about rich embeds, they currently don’t work with Twitter integration in Discourse:
As an alternative, this may be relevant to you:
If you are talking about standard oneboxes, I don’t know why it wouldn’t work natively unless you have changed onebox settings in your install, or your IP is blocked by Twitter for some reason.
I had this checked, and just unchecked it - but no changes in one boxing with twitter.
See here , below is what happens right now with twitter posts. I used to get the standard inbox, but perhaps I messed a config setting up? What might I have messed up?