Simplify Rate-Limit System: Unify to a Single x/hour Limit with Standard Headers

[Zingzy]

We propose refactoring our existing rate-limit system for endpoints that already enforce rate limits. Instead of our current multi-dimensional limits, we want to unify these to a single, configurable limit (denoted as "x" requests per hour, with the exact value to be decided later). This change will apply only to endpoints that currently have an existing rate limit, leaving endpoints without limits unchanged.

Additionally, we need to externalize all rate limit configuration settings to a separate config file (e.g., a .env file) rather than hardcoding them in the codebase. This will make adjustments easier across different environments and improve maintainability.

Proposed Changes:

• Unified Limit for Selected Endpoints:

  • For endpoints that already have a rate limit, enforce a unified limit of "x" requests per hour (value to be determined later).

• Standardized Rate-Limit Headers:

  • Ensure that every response from these endpoints includes:
    • X-RateLimit-Limit: Total allowed requests (e.g., "x").
    • X-RateLimit-Remaining: Requests remaining in the current window.
    • X-RateLimit-Reset: Time until the limit resets.
    • Optionally, a Retry-After header when the limit is exceeded.

• Externalized Configuration

  • Move all rate limit configuration (limits, window durations, etc.) to a separate config file (e.g., .env) rather than hardcoding these values.