Archive for April, 2013

Carlos Castaneda – Doubles

“Genaro at certain times is not Genaro but his double,” he said.

He repeated it three or four times. Then both of them watched me as if waiting for my impending reaction.

I had not understood what he meant by “his double.” He had never mentioned that before. I asked for a clarification.

“There is another Genaro,” he explained.

All three of us looked at one another. I became very apprehensive. Don Juan urged me with a movement of his eyes to keep on talking.
Read the rest of this entry »

Leave a Comment

Gift Card Downsides

This past weekend I went to Startup Weekend. We ended up doing my idea which was a way to buy people in need a meal at a local restaurant. Late Saturday night we pivoted to a more general concept of electronic gift cards.

The main difference being you get the money back when it expires. The use case that came up most often was wanting to provide money for children at college.

I’ve been thinking about the different ways the wealth transfer could work. I’m particularly interested in how it would be accomplished with bitcoins. So far I’ve got four scenarios. The players are the giver, the recipient and the vendor.

Read the rest of this entry »

Leave a Comment

Bitcoin Metadata

I’ve been thinking more about applications of the distributed ESON store. I’m very interested in the wealth distribution curve:

The 99.9% having 20% means that they would quintuple their wealth were it distributed evenly.

Something I think might be interesting to tackle the problem is to make a company mostly transparent. I’d like to use the ESON object to hold as much of the company data as possible. I’m primarily interested in the cost information.

It would pair especially well with bitcoins. Each transaction has a unique hash identifier and so you might have a subobject like:

  bitcoin: { transaction: {
    transaction hash: {
      for: product hash,
  } }

Read the rest of this entry »

Leave a Comment

Combining Objects

One of the things I want to do with the image library is combine repositories from multiple people. I’ve been thinking it could be as simple as an array of each of the repositories and then running:

var combo = $.extend.apply( this, $.merge( [ true ], objects ) )

Later entries override earlier ones, so this means entries should be in order of reliability.

Leave a Comment

Monetizing Content

I’ve been thinking about the distributed ESON object and what I would like to store in it. One of my first projects is an image library.

One of the things I would like is for people to be able to request royalties for use of their work. So, say for example that the artist who did the kitten head at the center of my logo would like a royalty for use of his image.

The first issue is how I know who the author of an image is. The sha1sum of the kitten head is 35813f6e. One approach would be to set:

 { royalty : {
  35813f6e: {
    holder: bitcoin address,
    price: float

As a person surfs the program keeps track of how much the requests are and can optionally pay them.

The issue is what is to prevent Bob from publishing a royalty for Alice’s work. This is where a consensus system comes into play. People include either Bob or Alice’s version in their individual trees and the one that is referenced the most wins.

That or you have a curator who somehow determines the validity of competing claims. That seems more brittle though.

Leave a Comment