Join activity is fine and we should use it
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The Follow/Accept/Reject issues listed in section B.1 are mostly due to not having collections for pending followers/following. That's what FEP 4ccd is for.
We could use the same model as FEP 4ccd for groups. An actor can have a collection of the join activities they have sent which have not been accepted or rejected; a group actor can have a collection of join activities that have been received and not accepted or rejected.
Best of all, it gives us a clean upgrade path from the Follow-based groups of FEP 1b12.
Contributor guide
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 reading the issue alongside the linked FEP 4ccd and the referenced FEP 1b12, then review section B.1's Follow/Accept/Reject discussion. Determine the proposed collections and their relationship to pending join activities; the work is done when the group model and upgrade path are specified clearly enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100