zlacker

[parent] [thread] 5 comments
1. comboy+(OP)[view] [source] 2023-07-01 20:29:37
Anybody knows if these requests were happening before the login only change? Because it would be hilarious if huge scrapping operation was a bug in their javascript.
replies(3): >>global+Kb >>samb17+Xi >>photon+5G
◧
2. global+Kb[view] [source] 2023-07-01 21:37:21
>>comboy+(OP)
I can say for sure that a certain flow ("back" from Profile view or similar) would trigger an infinite redirecting loop on Firefox on my Android device, with probably dozens of requests over a couple of seconds until rate limiting kicked in. Maybe there were many of these little bugs which together looked like some kind of DDOS or scraping.
replies(1): >>andrel+Pk
◧
3. samb17+Xi[view] [source] 2023-07-01 22:24:49
>>comboy+(OP)
I've noticed the frontend hammering the backend quite often in the past few weeks. It would not surprise me at all to learn that the "influx of scraping" was mostly Twitter's fault.
replies(1): >>ezoe+Q01
◧◩
4. andrel+Pk[view] [source] [discussion] 2023-07-01 22:41:30
>>global+Kb
Perhaps the engineers that understood how to analyze the logs were laid off?
◧
5. photon+5G[view] [source] 2023-07-02 01:55:03
>>comboy+(OP)
Some of the scraping was because Twitter fucked up the API so bots moved to scraping.

Dumb but obvious consequence

◧◩
6. ezoe+Q01[view] [source] [discussion] 2023-07-02 06:03:51
>>samb17+Xi
Are you suggesting Elon found out the true culprit the hard way?
[go to top]