Comments on: paying sideways http://gonze.com/blog/2010/02/13/paying-sideways/ internet music technology Wed, 01 Feb 2012 12:32:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Lucas Gonze http://gonze.com/blog/2010/02/13/paying-sideways/comment-page-1/#comment-5294 Lucas Gonze Tue, 16 Feb 2010 23:00:47 +0000 http://gonze.com/blog/2010/02/13/paying-sideways/#comment-5294 Tim, can you say more about how you used the adaptive payments thing? I didn't really get it from the docs. Tim, can you say more about how you used the adaptive payments thing? I didn’t really get it from the docs.

]]> By: sull http://gonze.com/blog/2010/02/13/paying-sideways/comment-page-1/#comment-5293 sull Tue, 16 Feb 2010 18:52:20 +0000 http://gonze.com/blog/2010/02/13/paying-sideways/#comment-5293 sorry, my meta tag code got parsed out of the post. but yes, auto-discovery meta tags for payment gateways.... sorry, my meta tag code got parsed out of the post. but yes, auto-discovery meta tags for payment gateways….

]]> By: sull http://gonze.com/blog/2010/02/13/paying-sideways/comment-page-1/#comment-5292 sull Tue, 16 Feb 2010 18:39:46 +0000 http://gonze.com/blog/2010/02/13/paying-sideways/#comment-5292 In reading your previous related posts, I was going to chime in with exactly what Jay Fienberg has suggested. I immediately think of how browsers handle RSS subscribing to how a Payment Transaction could be made. Also.... This assumes that the page represents a single purchasable object. Back in 2006, their was a proposal for rel=payment for more granular usage. It's also worth noting that crowdfunding is appropriate here. Meaning, your web app would be free and then you provide new features or game levels based on crowdfunding campaigns. if what you gave away for free is good stuff and garners a good following of fans/supporters, then a good percentage may be willing to contribute funds in order to get new stuff released. It's the same common tactic used within app stores etc. So it should not be ignored for the open web approach. Another thing to consider is media packaging technology that can control versioned dynamic network content. As you know, i've been paying attention to MAF (http://maf.mozdev.org) as a solution to test. What this may lead to is having browsers be able to have a web app manager as part of the addon/plugin framework. So you can "install" or "register" a web app into the browser and have versioning etc. So the Browser becomes an App Store. The public website is open and free but the installed/registered version has more exclusive access to content/features.... effectively the pro version of the website. Sull In reading your previous related posts, I was going to chime in with exactly what Jay Fienberg has suggested. I immediately think of how browsers handle RSS subscribing to how a Payment Transaction could be made.

Also….

This assumes that the page represents a single purchasable object.

Back in 2006, their was a proposal for rel=payment for more granular usage.

It’s also worth noting that crowdfunding is appropriate here. Meaning, your web app would be free and then you provide new features or game levels based on crowdfunding campaigns. if what you gave away for free is good stuff and garners a good following of fans/supporters, then a good percentage may be willing to contribute funds in order to get new stuff released. It’s the same common tactic used within app stores etc. So it should not be ignored for the open web approach.

Another thing to consider is media packaging technology that can control versioned dynamic network content. As you know, i’ve been paying attention to MAF (http://maf.mozdev.org) as a solution to test.
What this may lead to is having browsers be able to have a web app manager as part of the addon/plugin framework. So you can “install” or “register” a web app into the browser and have versioning etc. So the Browser becomes an App Store. The public website is open and free but the installed/registered version has more exclusive access to content/features…. effectively the pro version of the website.

Sull

]]> By: tim nutt http://gonze.com/blog/2010/02/13/paying-sideways/comment-page-1/#comment-5282 tim nutt Sun, 14 Feb 2010 05:21:51 +0000 http://gonze.com/blog/2010/02/13/paying-sideways/#comment-5282 I'm impressed with Paypal's new "Adaptive Payments". Very good stuff. Just integrated it and it seems to fit well in the listener/musician context. And could even become listener/label/musician/radio... split. I’m impressed with Paypal’s new “Adaptive Payments”.
Very good stuff. Just integrated it and it seems to fit well in the listener/musician context.
And could even become listener/label/musician/radio… split.

]]> By: Crosbie Fitch http://gonze.com/blog/2010/02/13/paying-sideways/comment-page-1/#comment-5281 Crosbie Fitch Sat, 13 Feb 2010 23:50:57 +0000 http://gonze.com/blog/2010/02/13/paying-sideways/#comment-5281 Four aspects: 1) Create a meta-payment system standard to enable PayPal et al to be integrated into the browser. 2) Facilitate the ability for the recipient of copies to pay the copyright holder. 3) Facilitate the ability for those interested in the production or development of intellectual work to commission the producer. 4) Provide a completely decentralised means whereby people can publicly declare financial transactions. It seems to me that Jay is addressing the first aspect. Flattr (cf Kachingle) and PaySwarm are addressing the 2nd aspect. I'm addressing the 3rd (along with surprisingly few others). The (distant) future is the 4th aspect (as per one of my previous comments). Four aspects:
1) Create a meta-payment system standard to enable PayPal et al to be integrated into the browser.
2) Facilitate the ability for the recipient of copies to pay the copyright holder.
3) Facilitate the ability for those interested in the production or development of intellectual work to commission the producer.
4) Provide a completely decentralised means whereby people can publicly declare financial transactions.

It seems to me that Jay is addressing the first aspect.

Flattr (cf Kachingle) and PaySwarm are addressing the 2nd aspect.

I’m addressing the 3rd (along with surprisingly few others).

The (distant) future is the 4th aspect (as per one of my previous comments).

]]>