Unblocking
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
As I was writing out the different actions in the Microsub spec, I noticed a pattern that was not complete:
- timeline
- channels
- search
- preview
- follow + unfollow
- mute + unmute
- block _+ unblock?_
It makes sense that there's also an `action=unblock`, for `action=block` has the same `GET` and `POST` as `follow` and `mute`, that would make such an unblock action possible.
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 with the Microsub specification's action definitions and compare block with follow and mute, including their GET and POST behavior. Confirm the proposed unblock action's request and response semantics and update the relevant specification text; done when the action is documented consistently and its behavior is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100