Feature Request: Client Plugin API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
It would be great if we could have client-side plugins like helpers for sending particular messages:
- Giphy
- Sticker Packs
Plugins like Giphy could be triggered with a /giphy command, and then the user would see a secure popup like:
Allow this plugin to access each message that is prefixed with /giphy and change the contents of the message before it's sent?
"Once" "Always" "Not Now" "Never"
Footnote: you can always change these settings under…
Plugins for Sticker Packs could be completely built via a URLs & a JSON file that only the sender would access. For security purposes, the sender could be responsible for downloading & embedding the images as attachments if we don't want to have a vector for sending URLs.
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
No repository files, tests, or entry points are named. Start by reviewing the linked Apple Messages documentation and the existing client architecture, then clarify the plugin API, permission flow, and Giphy or sticker-pack behavior. Done would require an agreed design and corresponding implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100