Open jlobos opened 6 years ago
My adblocker blocks all request to this endpoint, and I haven't had any issues so far. Hard to tell if they are really that necessary...
I think we should also look into /ajax/bz
. The client sends request to this endpoint quite often. Most of the time it's directly after /logging_client_events
.
We should investigate how we can reproduce the needed formData...
I'm currently looking into both endpoints and have had success with reverse engineering the /logging_client_events
endpoint, but I was wondering @timolins do you really think the /ajax/bz
endpoint is what they really use to detect bots or is it just that you haven't done anything aggressive enough on the site to trigger the spam "flag" or "filter" therefore your ad blocker blocking the /logging_client_evnts
endpoint is not an issue?
@AlexanderAryaAlikhani you told you had success with reverse engineering the /logging_client_events. Would you share your results with us? And can you tell anything about how Instagram detects bots so far?
The Problem is that when i try to log in to a account via script sometimes the accounts are banned or instagram often asks for a mobile phone number verification. I´m quite sure the accounts get banned because they are flagged as bots.
Furthermore i think the verification has something to do with the gdpr_s form data that i sent along with the request to create a account. This form data consists of an array that looks like this: [0,2,0, null]. As far as i know the second integer stands for the verification of your age, where the "2" means that you are older than 18 years. But what is with the two "0" and the "null"? Which information does hide behind that?
Thanks for any help in advance.
@AlexanderAryaAlikhani your research might be interesting.
@Stupefying Can you share your results on this mapping?
Proposed by @ibrunotome in https://docs.google.com/spreadsheets/d/1c5NITqvgL-4At54iL5k-KKx22BnBKUVF-wiN6FJDpHk/edit?disco=AAAABioFlso
https://graph.instagram.com/logging_client_events