Notifications channel order
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
A couple places in the spec it says the notifications channel must be first in the list:
When returning the list of channels, the notifications channel must always be the first in the list, as clients are expected to treat it separately such as showing it as a separate icon, not in the main channel list.
Is this really a necessary requirement? I never noticed this and I've been returning the notifications channel as the 2nd item. It seems to work fine with Microsub clients I've tested. Because the channel has a special uid, a client can take it out of the list and treat it separately if it wants, or not, and the order shouldn't matter.
Is there another reason it needs to be first, or can we update the spec to drop that requirement?
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
Review the quoted specification requirement about placing the notifications channel first and compare it with the observed Microsub client behavior described in the issue. Done means resolving whether ordering is necessary and updating the specification if maintainers agree to remove or revise the requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100