We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
Solved HTTP Error 429 Instagram
-
Hello, everyone
There still no answer??!
I will delete this topic in one week if no answer is submitted here
Please, this is important!
In last one week, only I that write on this thread, NO OTHERS!
Thank you for your attention. -
Extra information:
My Vivaldi version is now at Version 5.5.2805.38 -
Everyone that see/view this topic, please answer your question (if you can)... I'm desperate waiting for solution. I'm stressed if I not using Instagram for a long time.
But, I have a extra question:
If this issue is unsolved, how I mark it?
Thank you for your attention -
@frlvivaldi said in HTTP Error 429 Instagram:
If this issue is unsolved, how I mark it?
To mark a thread as Unresolved:
- Edit the first post
- Open the dropdown on the Submit button and click the radio button saying Ask As Question
- Submit the post again
To mark it as Resolved:
- Select the three dot vertical menu of the post that resolves the question
- Select the checkmark saying Mark This Post As The Correct Answer
-
As I think I said earlier, the problem you are experiencing is not caused by Vivaldi; and there is nothing we can do to fix it.
The block you encounter is set up by Instagram, and is very likely triggered by server-side algorithms that are looking for sequences of requests that Instagram's site developers consider undesirable, e.g. a script scraping content, which could have both performance consequences for the site (bandwidth, CPU, disk usage), and be considered potential copyright/license violations of the rights of the content creator whose content is being downloaded. Whether or not that is the intention of the the blocked user won't matter to Instagram.
They have probably set the trigger limit for a fairly low number of such actions before they block, since they want to quickly stop scrapers in their tracks, meaning that downloading the raw content (or whatever they detect) of just a relatively few images (may be 10, 20, I consider 100 unlikely) within a specific period (likely a few hours or a day) is likely to trigger the block.
I have no knowlegde about it, but there may be APIs available for such downloads for approved (read: paying) users.
Again, this is an Instagram policy, and it will trigger for all browsers if the algorithms they use observe requests they are coded to detect, and have nothing to do with Vivaldi.
-
@pesala and @yngve
Thanks for your answer, and is solved! But, if you have a idea, is there any forum or something else that I can ask about it?
This so will solve this problem efficiently.And thank you for all your efforts to help me through this topic. I'll learn from it, so I can use Instagram carefully. And now, I understand how HTTP Error 429 can happen and how to avoid it.
(Edit: Sorry for not checking the first post, I thought was unresolved. But, instead SOLVED! Thanks to Vivaldi Team! I now learn something important to my life!) -
This post is deleted! -
This post is deleted! -
PPathduck locked this topic on