3 ms·
Bug? - So I keep clicking another, and at some point ended up in a loop where I kept seen the same half dozen tweets or so. This is on OSX - Chrome: Version 34
by sophacles 13y ago
Bug? - So I keep clicking another, and at some point ended up in a loop where I kept seen the same half dozen tweets or so. This is on OSX - Chrome:
Version 34.0.1847.131
- TrainedMonkey 13y agoI think that is because they are using https://dev.twitter.com/docs/api/1.1/get/statuses/sample https://dev.twitter.com/docs/api/1.1/get/statuses/sample This is dev stream and it has tiny number of tweets.
- halisaurus 13y agoYes I think that was mentioned in the copy. It's also not really "random." It's one of the last 20 tweets globally. You probably won't ever see a tweet older than a few minutes.
- hmason 13y agoIt's actually because Twitter rate limits the oembed endpoint by IP, so the app caches the oembed codes and uses those if it gets limited. I've been meaning to flip that bit to the client but haven't gotten around to it yet.