<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Payments on Open Source Currency</title>
    <link>https://blog.opensourcecurrency.org/tags/payments/</link>
    <description>Recent content in Payments on Open Source Currency</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 May 2011 22:02:00 +0100</lastBuildDate>
    <atom:link href="https://blog.opensourcecurrency.org/tags/payments/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OAuth Scopes with UMA Action URLs</title>
      <link>https://blog.opensourcecurrency.org/2011/05/20/oauth-scopes-with-uma-action-urls/</link>
      <pubDate>Fri, 20 May 2011 22:02:00 +0100</pubDate>
      <guid>https://blog.opensourcecurrency.org/2011/05/20/oauth-scopes-with-uma-action-urls/</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;&#xA;&lt;p&gt;There is a new hope. Earlier this week, &lt;a href=&#34;http://blog.twitter.com/2011/05/mission-permission.html&#34;&gt;Twitter announced more precise controls over permissions&lt;/a&gt; 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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A simpler alternative to rel-payment</title>
      <link>https://blog.opensourcecurrency.org/2010/06/17/a-simpler-alternative-to-rel-payment/</link>
      <pubDate>Thu, 17 Jun 2010 02:16:00 +0100</pubDate>
      <guid>https://blog.opensourcecurrency.org/2010/06/17/a-simpler-alternative-to-rel-payment/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;http://www.opensourcecurrency.org/2010/06/opentransact-rel-payment-and-openid.html&#34;&gt;previous screencast&lt;/a&gt; may have tried to use too much technology to enable user-centric simple web payments.&lt;/p&gt;&#xA;&lt;p&gt;After looking around some, it occurred to me that the rel-payment microformat is not sweeping the world wide web. Using the Internet Archives, I found a blog post from July 2005 that announced &lt;a href=&#34;http://web.archive.org/web/20060906141521/http://www.pokkari.com/blog/2005/07/18/blip-supports-relpayment-now/&#34;&gt;support for rel-payment on blip.tv&lt;/a&gt;. I&amp;rsquo;m guessing not many people used this before it was abandoned.&lt;/p&gt;&#xA;&lt;p&gt;An alternative to rel-payment is to simply use a convention. For instance, the path /blog is a convention to quickly find the blog for a site. On Twitter, this would normally represent the person with the Twitter handle &amp;ldquo;blog&amp;rdquo; but Twitter follows the convention and redirects to blog.twitter.com.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
