Xevion / Xevion/dynamic-preauth
Rate Limiting
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 9d 3h
- Merged PRs (30d)
- 4
Description
The project has no protection against abuse and could be easily DoS'ed by someone spamming requests, which could get expensive fast. There's also no infrastructure for handling or communicating rate limits to users when they hit them.
Needs:
- Some form of request throttling/rate limiting
- User-facing feedback when requests are denied (error messages, toasts, etc.)
- Consider whether to use external protection (CDN/proxy) or build it in
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. First map where requests are handled and how denied requests are communicated to users, then evaluate the built-in Rust approach against the proposed CDN or proxy alternative. Done means abuse is throttled and denied requests receive clear user-facing feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100