Generic versus specialised servers
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 API client developer, I want to know if an API server will process and distribute arbitrary Activity objects or just a specific subset, so that I can know whether the server will work for my application."
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
The issue names no file, test, or entry point. Start by reviewing the repository's API specification and any existing treatment of generic versus specialised Activity objects, then define the expected server behavior and the documentation or specification change needed to make that distinction explicit.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100