Not surprised it's kinda wonky how it renders. Basically according to Twitter's docs I have to add some javascript for each embedded tweet that after the whole page renders and the javascript executes it reaches out to the Twitter API and gets the HTML to show the tweet and then updates the page to show the tweet.
I wanted to do it server side so it got the tweet code before rendering the page but that wasn't allowed according to their docs.. or it was but I wasn't allowed to do multiple requests for the same tweet in a short amount of time. Which meant I would have had to come up with a caching system to remember the code for a tweet for a while.. and I'm not a PHP developer.
I imagine that kind of thing makes it annoying for Tapatalk, I'm not sure if their app renders all the javascript or what.
__________________
Uncertainty is an uncomfortable position.
But certainty is an absurd one.
|