[blip.tv http://blip.tv/play/AYKm5RsA]

See this video on blip.tv.

This is a 10 minute explanation of the feature changes in the groupy branch. The motivation and design was discussed in RSpec And CanCan Authorization for Intentional Economics three months ago.

Not long after moving the Austin Time Exchange to Ruby on Rails, we started receiving requests for a groups feature since some local groups were interested in having their own currency but did not want to run their own instance of the software and their members were already on the existing system.

Since we’re a fork of insoshi, merging the groups feature from another fork is easy. Add some code to make simple payments per-group…Boom! Done.

Click To Play

“Anyone can run their own financial system.” - Bernard Lietaer at the Naropa Intentional Economics workshop.

Thanks to Lee Azzarello, oscurrency can now be deployed to heroku with the master branch. For production use, the edge branch is preferred as previous testing in development and production has been done with edge. Also, two more items need to be worked on for heroku deployment. In edge, search is done with sphinx which heroku does not support. Since a community currency system generally does not need industrial strength search, perhaps this can be replaced with standard database queries. Also, the edge branch uses workling and starling for background processing of newsletter and forum post emails. Heroku uses DJ workers.

[youtube http://www.youtube.com/watch?v=2r-1MiN3lY4&hl=en&fs=1&]

OAuth support with the OsCurrency API was first demonstrated in January. Ruby on Rails developers may have noticed that I didn’t use ActiveResource with OAuth. Instead, in both the January screencast and the Twitter OAuth Consumer screencast, we coded in raw JSON. This was a bummer because, as easy as it is to write JSON, it is difficult to test, maintain and support. It would be much better if we could use ActiveResource.

[youtube http://www.youtube.com/watch?v=R71jjP_0NR4&hl=en&fs=1]

The Columbia Exchange Circle was on TV yesterday…

“The idea of the exchange circle is to connect community members and get people to share the skills and resources that they have in a way that does not rely on the current economy,” said Maggy Rhein, another organizer for the C.E.C.

And members say that taking the program online is the easiest way to connect.

“People can post the request and people can see it instantly,” said Vince Foley, another organizer for the group and the Web site manager.

We interrupt our regularly scheduled program with a screencast for software developers.

If you are not a software developer, the screencast may not be useful, but it’s good to understand why OAuth is critical to online complementary currency. When you buy something online, you don’t log into your bank’s website to do the transaction. You may click on a PayPal purchase button or some other one-click button. So, a member may not want to log into a community currency website to make a payment to a peer. The community currency website needs to expose an application programming interface to third party applications (like Facebook) to make payments and execute other functions. How is the third party authorized to make a payment on behalf of the member? The OAuth protocol allows a member to seamlessly grant the third party application authorization to perform specific actions on his accounts, for instance. It’s kind of a big deal.

At One Web Day Austin on September 22, the idea was offered (see video in previous entry) that it would be relatively straightforward to build a complementary currency system on Insoshi. Shortly after that, Rich and I began a new project in github. The latest code can be found in the edge branch of Oscurrency.

Two weeks ago, the Austin Time Exchange made the switch to running this code. Most of the changes you see in github since then are the result of feedback from the members. This site runs on one 256M slice on slicehost.