<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Edgarcahn on Open Source Currency</title>
    <link>https://blog.opensourcecurrency.org/tags/edgarcahn/</link>
    <description>Recent content in Edgarcahn on Open Source Currency</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Nov 2007 04:42:00 +0100</lastBuildDate>
    <atom:link href="https://blog.opensourcecurrency.org/tags/edgarcahn/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Contingencies</title>
      <link>https://blog.opensourcecurrency.org/2007/11/09/contingencies/</link>
      <pubDate>Fri, 09 Nov 2007 04:42:00 +0100</pubDate>
      <guid>https://blog.opensourcecurrency.org/2007/11/09/contingencies/</guid>
      <description>&lt;p&gt;Last week, Rich and I gave a talk at &lt;a href=&#34;http://www.owasp.org/index.php/Austin&#34;&gt;OWASP Austin&lt;/a&gt;, the open web application security group. Social network security was the title. The main idea is how the health of social networks and communities can be compromised by attacking the identities - replacing identities known to the community with ones that are less functional. When identities are degraded or made more anonymous, then the community is at risk.&lt;/p&gt;&#xA;&lt;p&gt;Of course, we talked about complementary currency and among &lt;a href=&#34;http://ha.ckers.org/&#34;&gt;RSnake&lt;/a&gt;&amp;rsquo;s several good questions was how does a complementary currency system keep someone from taking too much. Of course, we mentioned the idea of putting a credit limit for each person in the code, but as everybody knows, it is less about the code than it is about the people and if the community is healthy and all the transactions are transparent, then people will police it themselves. If the community is sick, they won&amp;rsquo;t. Even for the hackers at the OWASP meeting who are immersed in code every day, this idea seemed agreeable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
