3 ms·
Did you block the script? The counter updates to 12 after the script runs, for myself. It is using a Twitter API at the back, so far as I can tell.
by shakna 9y ago
Did you block the script?
The counter updates to 12 after the script runs, for myself. It is using a Twitter API at the back, so far as I can tell.
- zuzun 9y agoIt gets blocked if you have tracking protection enabled on Firefox. The resource at “https://platform.twitter.com/widgets.js” https://platform.twitter.com/widgets.js” was blocked because tracking protection is enabled.
- simias 9y agoIt stood stuck at 0 for a while for me as well, before eventually updating. It's pretty crazy to see the amount of resources needed to load what is effectively a static page. I guess I shouldn't be too hard on a joke website but it's a bit symptomatic of the current state of the web these days.
- harryh 9y ago¯\_(ツ)_/¯ There is a TODO in there to calculate the timestamp based on the tweet id rather than digging through the tweet iframe after it loads. If someone wants to submit a pull request for that it should speed things up tremendously. Bitwise manipulations in JS are annoying though so I haven't bothered.