3 ms·

I'd be curious to know about other new ways to support payments.

fexl 17y ago
Here's a simple way to do it in Loom (https://loom.cc/faq https://loom.cc/faq). The customer visits a paid content site, let's call it https://valuable-information.com https://valuable-information.com. The customer's browser has a cookie for that site which stores a Loom location (an ID such as 1d425bd38f6520e6fab684a18b9c924e). A pile of assets sits at that location. When the customer views a paid article at valuable-information.com, the site debits that Loom location accordingly. Or, if the site uses a monthly charge, it debits the location once on the first of each month. The location also serves as an identity for storing the customer's preferences. When the balance gets low, the customer can "top off" the location however she likes. If she decides to stop using the site, she can sweep all the assets away from the location.
- thibaut_barrere 17y ago
  Thank you, that's interesting.
  - fexl 17y ago
    If you have further questions, feel free to email support@loom.cc, preferably encrypted with PGP.
  - fexl 17y ago
    I should also emphasize that this alleviates the "password proliferation" problem. The customer logs into her Loom folder using a passphrase she already knows. She creates a new Loom location there, nicknaming it "valuable-information.com" to remind her what it's for. Then when she signs up at valuable-information.com, she simply pastes the location into the sign-up form and presses Go. As long as her browser cookie lives, she never thinks about it again. If her cookie ever disappears, she just logs into her Loom folder, copies the location, and pastes it into the log-in form at valuable-information.com.
  - fexl 17y ago
    Because of this question I went ahead and wrote this little blurb on how to integrate Loom into shopping carts (and paid content sites): https://loom.cc/faq#shopping https://loom.cc/faq#shopping Thank you. That is all. :)
prawn 17y ago
The Flattr video isn't loading for me and there doesn't appear to be any other info there, so please excuse me if they're already running with the concept of guilt-micropayments. A half-baked idea I had (and emailed Ivan from TipJoy about ages ago) was the concept of a tip jar that accumulated funds based on pageviews from each specific user, then tried to encourage them to tip. Right now, a donate button on a blog will just have a flat approach - plain button, donate x, y or z, and that's it. I wondered if a content provider couldn't set a value for pageview (e.g., 2 cents for a blog post or forum topic), and then count per user. Following wording is off the top of my head and completely awkward, but you'll get the idea: "In the last month you've viewed 582 pages on mysite.com for a total of $11.64. Would you like to make a voluntary donation that reflects your use of the site?" Like I said, half-baked but could interest blog and forum owners enough for them to try it and virally spread the word.

fexl 17y ago

Here's a simple way to do it in Loom (https://loom.cc/faq https://loom.cc/faq). The customer visits a paid content site, let's call it https://valuable-information.com https://valuable-information.com. The customer's browser has a cookie for that site which stores a Loom location (an ID such as 1d425bd38f6520e6fab684a18b9c924e). A pile of assets sits at that location. When the customer views a paid article at valuable-information.com, the site debits that Loom location accordingly. Or, if the site uses a monthly charge, it debits the location once on the first of each month. The location also serves as an identity for storing the customer's preferences. When the balance gets low, the customer can "top off" the location however she likes. If she decides to stop using the site, she can sweep all the assets away from the location.

thibaut_barrere 17y ago
Thank you, that's interesting.
- fexl 17y ago
  If you have further questions, feel free to email support@loom.cc, preferably encrypted with PGP.
- fexl 17y ago
  I should also emphasize that this alleviates the "password proliferation" problem. The customer logs into her Loom folder using a passphrase she already knows. She creates a new Loom location there, nicknaming it "valuable-information.com" to remind her what it's for. Then when she signs up at valuable-information.com, she simply pastes the location into the sign-up form and presses Go. As long as her browser cookie lives, she never thinks about it again. If her cookie ever disappears, she just logs into her Loom folder, copies the location, and pastes it into the log-in form at valuable-information.com.
- fexl 17y ago
  Because of this question I went ahead and wrote this little blurb on how to integrate Loom into shopping carts (and paid content sites): https://loom.cc/faq#shopping https://loom.cc/faq#shopping Thank you. That is all. :)

prawn 17y ago

The Flattr video isn't loading for me and there doesn't appear to be any other info there, so please excuse me if they're already running with the concept of guilt-micropayments. A half-baked idea I had (and emailed Ivan from TipJoy about ages ago) was the concept of a tip jar that accumulated funds based on pageviews from each specific user, then tried to encourage them to tip. Right now, a donate button on a blog will just have a flat approach - plain button, donate x, y or z, and that's it. I wondered if a content provider couldn't set a value for pageview (e.g., 2 cents for a blog post or forum topic), and then count per user. Following wording is off the top of my head and completely awkward, but you'll get the idea: "In the last month you've viewed 582 pages on mysite.com for a total of $11.64. Would you like to make a voluntary donation that reflects your use of the site?" Like I said, half-baked but could interest blog and forum owners enough for them to try it and virally spread the word.