[browser extensions API] define scope of setRate, pay and updateBalance, enable, disable
Open
Nobody has claimed this yet.
specification
- Dominant language
- HTML
- Stars
- 607
- Forks
- 166
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 7
Description
setRate: so that the extension can set the default rate (and potentially a custom rate for a site/origin)pay: one-time paymentsupdateBalance: creating a new grant when grant is used up (or anytime as currently implemented in the WM extension)disable: disables payments (no monetization sessions get started)enable: enables payments (monetization sessions get started again)
Note that naming is not decided yet.
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 reviewing the proposed browser extensions API operations in this issue: setRate, pay, updateBalance, enable, and disable. Define the scope and naming for each operation, including how they affect grants and monetization sessions; done means the API responsibilities and names are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100