Rate limiting
Open
Nobody has claimed this yet.
user story
- Dominant language
- HTML
- Stars
- 33
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
"As an ActivityPub client developer, I want a reliable and standard way to discover rate limits in an ActivityPub API server, so I can avoid unexpected failures for my users."
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 files, tests, or entry points are identified. Start by reviewing the ActivityPub API Task Force repository and the seven existing issue comments, then research how rate-limit discovery is standardized for API clients. Done should mean the repository has an agreed, reliable way for clients to discover server rate limits.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100