Acutally I never understood why the tweets posted in a thread seem to "disappear" after a while. Did I get it right that it just takes a while to reload?

[Link]

Twitter doesn't want sites hammering their servers loading data over and over. They want sites to store some of the Tweet info locally. They provide a variable "time to live" (TTL) value for this Tweet data. We kinda ignore the TTL and only refresh Tweets once every 30 days. Tweets go away for lots of reasons: the Twitter user deletes a Tweet, their Twitter account is banned/suspended, etc. Lots of adult entertainment Twitter accounts get banned by Twitter for violating their terms of service. That's the primary reason for many of the Tweets here in the forum going to some version of "unavailable".

[Link]

Edited to add: I just downloaded and installed Firefox from the Google Play Store and it appears to be properly lazy-loading tweets.

Edited by - Drew Black on 1/4/2021 4:19:17 AM

[Link]

Edited by - morbidthoughts on 1/4/2021 3:38:34 PM

[Link]

I'll do a little tinkering. I'm not logged into twitter for the web on my phone which makes the Tweets render as though I'm an anonymous Twitter user without an account. (I don't even have the Twitter app on my phone.) I'm curious if there's a bug in the Twitter JS libraries that render Tweets with their API.

[Link]

I've disabled all ad/tracking blockers and whitelisted the ADT website, but they still won't load.

[Link]

Desktop Firefox works fine with or without the shield.

[Link]

I have attached the settings for Desktop for you to look for under Options under Privacy & Security:

[Link]

The issue is still happening today, so it was happening both before and after the new FF update.

[Link]

I'll check it from a different ISP soon. I'm on Starlink at the home office now.

[Link]

Watching the waterfall in the network tab using a developer tools window shows the delay appears to be happening within Twitter's code that inserts and inline Iframe and renders the tweet within the forum page.

I use the Intersection Observer API to lazy-load the Tweets as a user scrolls down the page. I'm going to see if maybe the new version of FF has a slightly different IO API implementation and is slow to detect the tweet placeholder moving into the visible area before firing the event that loads the Tweet content.

edited to add:

I've watched the page loading more closely. The Twitter script that injects the embedded Tweet iframe's CSS & html is loading very quickly. Something in FF is preventing the resources in that iframe from being fetched and rendered quickly. I'll take a look at it a bit more but at the moment I don't think there's much I can do to speed it up because the scripts that load the Tweet content come from Twitter's servers.

Edited by - Drew Black on 12/14/2021 7:38:32 AM

[Link]