Add background task to update Discord model upon user login for existing users

[Copilot]

Analyzing Discord rate limiting concerns raised in PR comments and planning solution.

Analysis Complete

• Understand the rate limiting concern
• Analyze current Discord API usage patterns
• Review Discord model fields and update frequency needs
• Run ruff format on code files
• Add timestamp tracking for Discord data updates
• Implement time-based throttling for Discord updates
• Update background task to respect throttling
• Add configuration for update frequency
• Test the rate limiting solution
• Reply to comments with implemented solution

Rate Limiting Concern

The concern is valid: current implementation makes Discord API calls (/users/@me) on every login, which could hit Discord's rate limits (typically 5 requests/5 seconds) during high traffic periods.

Planned Solution

Implement time-based throttling:

1. Add last_discord_update timestamp to DiscordModel
2. Only update Discord data if >24 hours since last update
3. Preserve immediate updates for new users
4. Make update frequency configurable

Code Formatting

• Applied ruff formatting to all modified files per feedback

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jontyms]

Rate limiting concerns me

[jontyms]

@copilot Consider discord rate limits

[jontyms]

@copilot Consider discord rate limits

[jontyms]

@copilot also run ruff format

[Copilot]

@copilot also run ruff format

Done! Applied ruff formatting to all files. The formatting changes include quote normalization, trailing comma addition, and whitespace cleanup. Commit: 75f0f54