CORS
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 a Web client developer, I want to have reliable expectations for CORS for the ActivityPub API, so that I can use API endpoints from the browser without going through a proxy server."
This is one of the hard parts of working with the API right now.
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
Start by reviewing the ActivityPub API endpoints and the issue's browser-use case to identify what CORS behavior currently exists and what expectations are missing. Done means the API's CORS behavior is explicitly defined and reliably supports the intended browser requests without a proxy.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100