<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oauthactiveresource on Open Source Currency</title>
    <link>https://blog.opensourcecurrency.org/tags/oauthactiveresource/</link>
    <description>Recent content in Oauthactiveresource on Open Source Currency</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jun 2009 03:56:00 +0100</lastBuildDate>
    <atom:link href="https://blog.opensourcecurrency.org/tags/oauthactiveresource/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stupid Currency Tricks: Payment Dropbox with OAuthActiveResource</title>
      <link>https://blog.opensourcecurrency.org/2009/06/30/stupid-currency-tricks-payment-dropbox-with-oauthactiveresource/</link>
      <pubDate>Tue, 30 Jun 2009 03:56:00 +0100</pubDate>
      <guid>https://blog.opensourcecurrency.org/2009/06/30/stupid-currency-tricks-payment-dropbox-with-oauthactiveresource/</guid>
      <description>&lt;p&gt;[youtube http://www.youtube.com/watch?v=2r-1MiN3lY4&amp;amp;hl=en&amp;amp;fs=1&amp;amp;]&lt;/p&gt;&#xA;&lt;p&gt;OAuth support with the OsCurrency API was first &lt;a href=&#34;http://www.opensourcecurrency.org/2009/01/stupid-currency-tricks-with-oauth.html&#34;&gt;demonstrated in January&lt;/a&gt;. Ruby on Rails developers may have noticed that I didn&amp;rsquo;t use ActiveResource with OAuth. Instead, in both the January screencast and the &lt;a href=&#34;http://www.opensourcecurrency.org/2009/02/stupid-currency-tricks-twitter-oauth.html&#34;&gt;Twitter OAuth Consumer&lt;/a&gt; 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.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
