Twitter/X issue
Posted: Sat May 18, 2024 11:48 am
Amped has identified a problem with embedding X/twitter posts into jplop threads.
Until today, the default domain for X/twitter was still twitter.com. So if you copied a tweet it would say, for example:
https://twitter.com/JuiceJuice_uf/statu ... 0300514630
and you could use the tweet bbcode button to change that into an embed. But now, the default domain for X/twitter is x.com, so the tweet will show up in the browser as
https://x.com/JuiceJuice_uf/status/1791361690300514630
However, this does not work as an embed. Why? Because X still hasn't updated all the backend plumbing ans still expects tweets to be embedded with twitter.com urls.
When people use X's embed tool to embed a tweet into a full html website, it will automatically convert x.com posts to twitter.com posts that can be embedded.
But for bbcode there is no conversion facility, so for now, we have to manually change x.com posts back to twitter.com and then use the tweet button.
I imagine at some future date X will update their embeds so that a straight x.com tweet can be embedded, but for now, we have to manually change x to twitter in the url for it to work properly.
I'll continue to look for more user-friendly solutions to this problem.
Until today, the default domain for X/twitter was still twitter.com. So if you copied a tweet it would say, for example:
https://twitter.com/JuiceJuice_uf/statu ... 0300514630
and you could use the tweet bbcode button to change that into an embed. But now, the default domain for X/twitter is x.com, so the tweet will show up in the browser as
https://x.com/JuiceJuice_uf/status/1791361690300514630
However, this does not work as an embed. Why? Because X still hasn't updated all the backend plumbing ans still expects tweets to be embedded with twitter.com urls.
When people use X's embed tool to embed a tweet into a full html website, it will automatically convert x.com posts to twitter.com posts that can be embedded.
But for bbcode there is no conversion facility, so for now, we have to manually change x.com posts back to twitter.com and then use the tweet button.
I imagine at some future date X will update their embeds so that a straight x.com tweet can be embedded, but for now, we have to manually change x to twitter in the url for it to work properly.
I'll continue to look for more user-friendly solutions to this problem.