[ Suggestion ] Update logic to be compatible with Mino v5

[Calemy]

Is your feature request related to a problem? Please describe.
Hey, as you are probably aware i'm the creator of mino!
First, i want to say thank you for integrating our mirror in your application, really means a lot.
I'm here to give a heads up about a major update that is coming very soon.
We implemented new Ratelimits and now return new headers on downloads which we'd greatly appreciate if you could implement those changes so both you and us can keep a smooth user experience.

Describe the solution you'd like
on downloads please check for following headers:

x-ratelimit-remaining
x-ratelimit-reset
x-daily-remaining
x-ratelimit-daily-reset

if x-ratelimit-remaining or x-daily-remaining hit 0 or below, please wait the remaining time that is being returned in seconds on the header.

if you do end up running into a 429 please check the retry-after header and again, wait the remaining time that is being returned on the retry-after header and retry the request.

Describe alternatives you've considered
There is no alternative

Additional context
We expect this update to fully roll out by Friday, July 11th at 15:00 UTC
Hope you can work with the details that i gave over here

[roogue]

Hi!!

Thank you so much for creating such a beautiful, user-friendly, and free service. I'm truly grateful and osu-collector-dl will absolutely stay aligned with your updates moving forward. The introduction of header-based rate limit handling is a great improvement and will definitely help in developing a smarter client.

I do have a small request, which I’m sure you’ve already considered. Due to my ongoing finals (again), I won’t be able to update the client until the end of this month. I was wondering if the “old” rate limit handling API could remain functional for at least a few more months to allow some buffer time for the transition.

Thanks again for your hard work and dedication! :)

[Calemy]

Thank you for bringing your concern up to our attention. I'll make sure to temporarly re-implement the old route structure back into version 5 to give yourself some buffer time while you're in your finals.

Good luck and much love! <3

[roogue]

Hey! While implementing the new rate limit handling system, I had a quick question:

Will the api/ratelimits endpoint still be available and not deprecated in the new version of your API?
I need to check the remaining quota before the user starts fetching beatmaps, to avoid a case where they initiate a full download only to discover they’ve run out of credits.

[roogue]

Also, upon testing, only x-ratelimit-remaining header was returned from your /d/ endpoint, is there anything I overlooked? or is the new update wasn't fully rolled out yet?

[Calemy]

Hey roouge, i apologize for the late response but i'm here to share some insight.
Due to some internal miscommunication, we have not yet rolled out the new version like we planned on doing.
As of right now; we have not deprecated the /api/ratelimits endpoint, due to some concerns that have not yet been fufilled to our satisfaction. If there are any changes, we'll make sure to give a proper heads up!

Hope you can forgive us for the hiccup with the release date and thanks for reaching out!

[FexisGuro]

An error occurred: Error: 17:40:12 | [OcdlError]: REQUEST_DATA_FAILED - Error occurred while requesting data
Error: 17:40:12 | [OcdlError]: REQUEST_DATA_FAILED - Error occurred while requesting data
Error: read ECONNRESET. What is the reason for this message?

[roogue]

Hi @FexisGuro, this is likely the same issue as #40. It usually means your IP has been blocked by the download provider, possibly due to using services like Cloudflare WARP.

It would be better to open a new issue instead of commenting on an old one so it can be tracked properly.

[FexisGuro]

Is there a way to fix this? And I'm sorry, but I don't understand git hub.