session payments: compute payment delay and amount algorithm #24
Conversation
section/session-flow.html
Outdated
| <li>Let |secondsInMonth:double| be <code>30 * 24 * 60 * 60</code>.</li> | ||
| <li class="note">A "month" is treated as a fixed 30-day period for payment pacing calculations.</li> | ||
| <li>Let |defaultPaymentAmountPerSecond:double| be <code>|maxRateOfPayPerMonth| / |secondsInMonth|</code>.</li> |
There was a problem hiding this comment.
The extension has an hourly rate of pay. The monthly rate (not same as monthly budget) might be less useful, under the assumption that 30*24*60*60 is not the time user may spend in browser (why not something like 8h a day, not 24h a day?). So, we went with a lower resolution (hourly rate). It does mean user has to configure both these values. The extension by default uses $5 for monthly budget, and $0.60 as hourly rate. https://github.com/interledger/web-monetization-budget-suggestions includes recommended budgets for various currencies.
There was a problem hiding this comment.
I was thinking of a monthly rate as a way to simplify the logic and streamline the UI, since the only thing the user needs to provide is the max cap they never want to exceed. Using a 30×24×60×60 formula assumes continuous 24/7 streaming but as long as it represents the upper limit, it's probably ok. I like it because the logic stays straightforward.
I’m also fine with having both an hourly rate and a max cap if that’s the direction we want to go. Do you want me to change to hourly rate and monthly limit? Shall those be supported by UI, correct?
There was a problem hiding this comment.
I understand the rationale. I guess it shouldn't matter much right now.
In future, users will definitely want to customize the rate, even per-site basis. So having an hourly rate is likely better for that.
There was a problem hiding this comment.
I understand the rationale. I guess it shouldn't matter much right now.
In future, users will definitely want to customize the rate, even per-site basis. So having an hourly rate is likely better for that.
No description provided.