The ?__a=1 loophole on Instagram has broken, what should I do now?

Question

Instagram

For years I used this feature for Instagram feeds, so as not to bother customers with tokens, today everything is broken, in responses there is an error 302.

Answer 1

Judging by the requests, it's been like this for two years.
They also recently tried to make a parser for a telegram bot, but in the end they received only a page with a login instead of data. Although in the browser everything was OK. I found this explanation on the stack:

Actually it is not really banned but now redirects with 302 to auth page. It seems like auth is required when Instagram account and query geoIPs are different. Alternative is to use the official API. No scraping can be done, because the profile link now also requires authentication. You can do authenticated scraping but you are limited to 200 queries ( that Instagram sends to get data) per hour.

The only way out is probably to parse the entire page and look for what you need among the tags. There will be less data.