The oscurrency fork at https://github.com/bace/oscurrency/ is running on Rails 6.1 and works with heroku.

There is a Rails 5.1 fork at https://github.com/bace/oscurrency/ which works with heroku.

Disclaimer: I am deliberately avoiding edge cases and other costs of Bitcoin.

Bitcoin (BTC) is a relatively new system and we often make sense of new systems by drawing on familiar experiences to describe them, so it is natural to draw on experience with dollars and gold to understand Bitcoin. Like an ounce of gold, the price of a bitcoin can be measured in dollars. As the price of a bitcoin skyrocketed in 2013, it became a famous asset like dollars or gold but the current price of a bitcoin does not have much to do with why it is useful. Over most recent interval ranges, bitcoins do not seem to offer any advantage as a store of wealth. So, what’s curious about Bitcoin is that what it seems to be famous for is not why it is useful.

Mobile Responsiveness FTW! We just closed our milestone in github this week. Thanks to all contributors, Tom Brown, Ziyan, rewritten, acao.
A note from Tom Brown about the Bootstrap Process:

in issue 185 (jan 10), @acao explained "I would love to help with a snazzy
twitter bootstrap UI implementation as well...Our project is nearing
launch, and we would LOVE to have mobile responsiveness built-in, and a
nice clean bootstrap UI strategy...bootstrap/sass are sooo powerful!"

@herestomwiththeweather replied "i'm probably not qualified to set up
"bootstrap-sass and all the other assets handling all set up" though. maybe
someone else will step up to get this ball rolling."

The next day, the initial set of commits were delivered by @rewritten: "Check
the https://github.com/oscurrency/oscurrency/tree/bootstrap222 branch. I've
added external bootstrap files, font-awesome, and swapped the legacy tabs
with the bootstrap's ones (they weren't working)."

on Feb 1, the google group was given notification of this effort with the
justification that the efforst was "to improve the user interface (and
especially for mobile devices)":
https://groups.google.com/forum/#!topic/opensourcecurrency/Fo2DM43Ohgg

the bootstrap effort was idle until the end of june when a milestone was
created for a collection of bootstrap issues:
https://github.com/oscurrency/oscurrency/issues?milestone=1&page=1&state=closed

at the end of july, the google group was given notification that the
bootstrap branch would be merged into master:
https://groups.google.com/forum/#!topic/opensourcecurrency/izHfKPrIPuU

the twitter bootstrap project page is at http://getbootstrap.com/

cheers,
tom

Welcome to OS Currency on wordpress!
From the opensourcecurrency google group (10/3/13):

Over the last year or so, while github participation (issues, some 
documentation and one virtual dev meetup announcement) has increased, the 
opensourcecurrency.org blog has sadly been inactive.

While the blog has been performing solidly as an archive of old posts, with 
some help, it could also offer a more welcoming experience and opportunity 
for mutual support among people who are interested in oscurrency.  

Here is the good news.  Amy Kirschner has been using oscurrency for almost 
a year for B2B mutual credit exchange and has suggested that wordpress 
would offer more functionality (than blogger) and allow easier access for 
participation from admins (rather than coders).  As Amy uses oscurrency in 
support of vbsrmarket.com, she is especially interested in usability and 
the community around the software.

Even though there are some details to work out (e.g. wordpress.com vs. 
self-hosting), it seems reasonable to switch the blog in a week or so.  

There is no change in existing process: software development issues are 
still discussed on Github with logistical/upgrade issues promoted to this 
Google group.  Also, there is clearly a need to improve the documentation. 
 Please feel free to use Github issues to identify gaps in the 
documentation.  There are many.  If you are not comfortable with using 
Github, another alternative is to blog about any problems (or any 
experiences in general) you are having with the software.  Additionally, as 
this Google group is a low traffic mailing list, it seems likely there will 
be a need for an additional higher traffic forum like discourse.

Thanks in advance for any suggestions.  Have a great weekend!

-Tom

[youtube=http://www.youtube.com/watch?v=EZefmK1tndc&w=560&h=315]
Update (June 15): Cyberwire on Google Play App Store
Cyberwire is an open source proof-of-concept for OpenTransact on Android. In the screencast, we see the Android app used to transfer 10 imaginary coffeebucks using one OpenTransact provider implementation. Even with a different OpenTransact provider implementation, we see the same functionality accessed by the same Android app.
OAuth Dynamic Client Registration Protocol is used to allow the Android app to start communicating with a new OpenTransact provider. A custom application_type request parameter is set to “noredirect” to indicate to the provider that instead of the client providing its own redirect_uri, the provider should choose a uri within its own domain and after authorization, the client will snarf the authorization code parameter from that uri instead of its own.

[blip.tv http://blip.tv/play/AYLP3wMA width=“480” height=“405”]

In this screencast, we’ll improve the code introduced in the previous post OAuth Scopes with UMA Action URLs with the help of our friends Artifice and Cucumber.

Calls to Net::HTTP can be intercepted by Artifice and sent to your rack application instead of the network. If you are developing an OAuth provider, Artifice makes testing the api a lot easier. Since the OAuth ruby gem uses Net::HTTP, we can wrap Artifice blocks around our client calls in tests and Artifice will intercept the calls and route them to our Rails app.

In a recent South Park episode, Kyle is kidnapped and subjected to product prototyping (made of people) by employees of a large, cult-like tech company who explain that it is all justified: Kyle failed to read the complex terms and conditions he agreed to. Unfortunately, the risks of consenting to the agreement were not clear to Kyle.

There is a new hope. Earlier this week, Twitter announced more precise controls over permissions granted to third parties. Twitter wants to make the risks of consent more clear. Access to your direct messages should be on a need-to-know basis. Twitter says that by mid-June, when you grant a third-party permission to your twitter account, it will no longer be able to access your direct messages unless you have explicitly granted that particular type of access.

[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.

[vimeo 19407702 w=400 h=300]

The Health Class: Dr. Ted Norris interviews Sheila Gordy, Austin Time Exchange on Vimeo.