Not for me
1 Like
Nope, work laptop, AlwaysOnVPN, Chrome
Phone is fine Chrome
Pixel Slate no worky, normal WiFi, Chrome
Remoting on to my Work PC and it doesn’t work on there either, Chrome or Chromium Edge, strangely IE11 does works
Odd.
ISP?
Although IE wouldn’t work if it was ISP related.
Plugins in Chrome - ad removal, flash disablers, etc.?
Have you turned off Flash early - Chrome will withdraw support soon but you can turn it off.
Do other videos in tweets ever work?
I’m guessing at the moment on all of these.
When you get a mo could you open Chrome developer tools and see if there are any obvious errors in the console and, if you know how, follow the page resources (of which that video will be one) to see if anything untoward is happening as it downloads.
Strangely the tweet is now showing!!! Can’t troubleshoot it if it works, might have something to do with visiting Twitter…
I’ve moved everything here to stop cluttering up the “joke” thread…
Is it to do with those tweets only showing if you’re logged in to Twitter?
Logout of Twitter and try again?
I’m always logged into Twitter
I dont have twitter at all.
1 Like
Wtf is my Twitter password no way logging out@
Logged out of twitter and they’re all still showing…
Don’t you use a password manager??? and I don’t mean a post-it note
I did until I forgot my password yo it 
Actually until my last job when zIt Security got at my phone & new laptop.
That bug seemed to come after Android & last Discourse downtimes/upgrades
Nah, I’ve been experiencing it for a while, and not just on my phone. I think it’s more twatter related than Discourse or OS…
Well, I can’t do anything until it stops working for you, Bob.
There is a discussion about Facebook, Reddit and Instagram videos sometimes failing to embed on Discourse but that was fixed 6 days before I did the last update.
I could try to update the site and see if it fixes it but my inclination is to try to track it down.
What is confusing me is that it doesn’t work then works. That suggests it’s environmental for each user experiencing the problem.
Broadly the same environment, different times, different results.
You need to track and trace
2 Likes
tl;dr This could be rate limiting on the Twitter API so would only appear at ‘busy’ times.
For everyone that has seen this issue, does it sometimes work and sometimes fail. Or, for a given Tweet, does it always fail?
Back in the early days of Twitter I used to do a lot of API programming. You may remember my word clouds - Wordles on Saintsweb. Anyway, if you used the Twitter API a lot it would rate limit. You had a finite resource limit in, say, a minute, and if you used it up it would wait for the next minute before giving you more API time.
This has that sense to it for me.
I’ll need to find a case when this doesn’t work and look at the error we’re getting back from Twitter - that’s where you come in Bob.
I’m developing an App at the moment that I need 67% of Sotonians to install on their smartphones ('slowlane is given a pass).
It will tell me every time a poster’s finger goes within 2cm of their arsehole.
You better keep your phone charged, Fatstuff.
3 Likes
1 Like