3 ms·
Here is how you verify it yourself, curl https://twitter.com/zarfeblong/status/1339742840142872577
by klodolph 6y ago
Here is how you verify it yourself,
curl https://twitter.com/zarfeblong/status/1339742840142872577
- ALittleLight 6y agoStill possible to curl, just looks like it is a bit more obnoxious now and requires parameters like your browserAgent and cookie to be set. Look in your network tab for requests to an endpoint like this[1] with a lot of query parameters after. 1- https://twitter.com/i/api/2/timeline/conversation/<twitter https://twitter.com/i/api/2/timeline/conversation/<twitter status id>.json
- ignoranceprior 6y agoAny HTTP request you can make with a browser can in principle be made with curl. The issue is that seeing content now requires you to jump through lots of hoops, whereas it was previously openly accessible by default.
- ALittleLight 6y agoThat's true. I agree it is a worse change and obnoxious for twitter to do (unless there is some easy way I/we just aren't aware of that lets you easily get the tweets as before).
- voltagex_ 6y agoAs pointed out by https://twitter.com/magusnn/status/1339833122456662017 https://twitter.com/magusnn/status/1339833122456662017, you can impersonate GoogleBot and get an eye-watering 500kb of HTML to read a single tweet.