Is your feature request related to a problem/ issue? Please describe.
To ensure that all visits are recorded flawlessly by adding records to the queue.
Describe the solution you'd like
When the Wayback Machine auto-save feature is turned on, all requests are added to a list called "queue" in the Browser Storage area for situations such as when the "Save Page Now" button is pressed to save this page.
When it receives errors such as rate limit, it calculates with the last save time and keeps the information of the nearest request time, or if the API offers this, it remains in standby mode until that time and continues to add new connections to the queue.
It continues to send requests when the time comes. In this way, all pages visited by the user (taking into account the blacklist details they have specified) are transmitted to the Wayback Machine API and recorded.
Describe alternatives you've considered
Since this solution is client-side, if a queuing structure is created in the wayback machine API (probably there is, but such a feature is needed due to user limits) and all incoming requests are processed, there may be no need to develop a wayback machine extension.
Additional context
Maybe a page where this list (Queues) can be seen would be nice.
I am open to comments, my goal was to have to wait and try again and again for the sites I really wanted to register. I think why not create a software solution for this in the age of technology :D
Is your feature request related to a problem/ issue? Please describe.
To ensure that all visits are recorded flawlessly by adding records to the queue.
Describe the solution you'd like
When the Wayback Machine auto-save feature is turned on, all requests are added to a list called "queue" in the Browser Storage area for situations such as when the "Save Page Now" button is pressed to save this page.
When it receives errors such as rate limit, it calculates with the last save time and keeps the information of the nearest request time, or if the API offers this, it remains in standby mode until that time and continues to add new connections to the queue.
It continues to send requests when the time comes. In this way, all pages visited by the user (taking into account the blacklist details they have specified) are transmitted to the Wayback Machine API and recorded.
Describe alternatives you've considered
Since this solution is client-side, if a queuing structure is created in the wayback machine API (probably there is, but such a feature is needed due to user limits) and all incoming requests are processed, there may be no need to develop a wayback machine extension.
Additional context
Maybe a page where this list (Queues) can be seen would be nice. I am open to comments, my goal was to have to wait and try again and again for the sites I really wanted to register. I think why not create a software solution for this in the age of technology :D
Click to "Save Page Now" at 2-3 min later:
Reference