Product / Project management and development. Focusing on making web audio and video accessible and media literacy with Hyperaudio. 2012 Knight Mozilla OpenNews Fellow.
More generally the thing about adding a payment pointer "injecter" to libraries and plugins is that the the author gets paid in proportion to how much those modules are used by visitors to the site that they're used on.
Kind of obvious but pretty revolutionary at the same time. Especially as the owner of the website using the plugin does not have to shell out anything in advance (which could be a barrier to some).
I'm not sure if the stipulation to keep payment pointer code intact could co-exist with an open source license – I guess it could.
I suppose the issue would be when the website is already taking advantage of Web Monetization and doesn't want their payment pointer overridden!
I wish we'd had this mechanism available to use when we released jPlayer all those years ago – it ended up getting used by Pandora!
For further actions, you may consider blocking this person and/or reporting abuse
More generally the thing about adding a payment pointer "injecter" to libraries and plugins is that the the author gets paid in proportion to how much those modules are used by visitors to the site that they're used on.
Kind of obvious but pretty revolutionary at the same time. Especially as the owner of the website using the plugin does not have to shell out anything in advance (which could be a barrier to some).
I'm not sure if the stipulation to keep payment pointer code intact could co-exist with an open source license – I guess it could.
I suppose the issue would be when the website is already taking advantage of Web Monetization and doesn't want their payment pointer overridden!
I wish we'd had this mechanism available to use when we released jPlayer all those years ago – it ended up getting used by Pandora!