RE: "Is a browser extension really needed? Why can't the user authorize a backend to send payments to a pointer?"
Web monetization is "pay as you go" meaning the back end needs to know if you are engaged with the content in order to keep the payment stream going to the content site. i.e. it is session based.
Without that session/connect mechanism then we are back to the subscription model.
Although, I agree with the spirit of your comment. I think there needs to be other (better?) ways for users to control the payment stream.
Not sure if you are talking about sending or receiving payments.
I haven't parsed all the architecture yet, but I think for sending payments yourself would be something like this github.com/interledgerjs/ilp-wm-pr...
You would have to run moneyd for your own wallet and a bunch of infrastructure yourself
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
RE: "Is a browser extension really needed? Why can't the user authorize a backend to send payments to a pointer?"
Web monetization is "pay as you go" meaning the back end needs to know if you are engaged with the content in order to keep the payment stream going to the content site. i.e. it is session based.
Without that session/connect mechanism then we are back to the subscription model.
Although, I agree with the spirit of your comment. I think there needs to be other (better?) ways for users to control the payment stream.
Thanks for your comment Dave.
Would it be possible to use WebSockets or polling an HTTP endpoint depending on what kind of frequency of payments you're looking for?
Not sure if you are talking about sending or receiving payments.
I haven't parsed all the architecture yet, but I think for sending payments yourself would be something like this
github.com/interledgerjs/ilp-wm-pr...
You would have to run moneyd for your own wallet and a bunch of infrastructure yourself