RocketChat / RocketChat/Rocket.Chat
[NEW] Send 'mutable-content = 1' in APN payload
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
This will allow us to support end-to-end encrypted notifications & also remove markdown in the client side.
Documentation:
Example payload:
{
“aps” : {
“category” : “SECRET”,
“mutable-content” : 1,
“alert” : {
“title” : “Secret Message!”,
“body” : “(Encrypted)”
},
},
“ENCRYPTED_DATA” : “Salted__·öîQÊ$UDì_¶Ù∞è Ω^¬%gq∞NÿÒQùw”
}
This will also require work in https://github.com/RocketChat/push & https://github.com/RocketChat/pushgateway
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 with the Apple notification-modification documentation linked in the issue, then inspect the APN payload path in Rocket.Chat and the related Rocket.Chat/push and Rocket.Chat/pushgateway repositories. Done means the payload includes mutable-content = 1 and the dependent encrypted-notification work is supported across the referenced services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100