For awhile after Elon initially broke embedded tweets altogether, we had a workaround where tweets would embed inline as the page loads, which…
pro: tweets look just like they did on Twitter
con: they load with some delay after opening a thread, they could make the thread jump around
Now, it seems like Discourse has half-fixed tweet embedding, which…
pro: like before, it’s baked into posts (no delay, no jumping) and shows tweet text
con: unlike before, it’s now missing media (images/video) and quoted tweets, and like before it’s missing embeds (like, if the tweet links to a news story, Twitter would show a preview of that link but Discourse does not)
I’m curious if people have a preference between these two systems, as we should be able to ditch the Discourse embedding and stick with the workaround version if people prefer it.
I’m going to abstain since it’s a close call. The jumping is really irritating, especially in some threads that are lots of tweets (the Ukraiine thread usually jumps backward by about 8-10 posts). OTOH, full embedded tweets are very very nice. #BASTARD
The jump is extremely irritating on mobile but I havent complained because I know there must be technical magic getting them to display. Lots of sites are having issues. I vote less jump, because I can always go to the tweet link if I need to see media.
Given the strong preference expressed so far, I’ve changed it back to the old (full embed) behavior for now. Happy to revisit as features & preferences change.
I would prefer the old behavior other than it not working half the time for me. If I go to twitter I’m logged in, is there something else I need to do?
Sometimes I feel like it wasn’t particularly fast but would eventually load? Especially in threads with lots of tweets, I don’t know that there was a science to which ones loaded first, so maybe delays made it seem like it’s not working? Being logged in to Twitter on the same browser you’re using for SPE should def help.