Met a guy behind Open Transactons at a party this past weekend. The way he explained it, it looks like OP can do everything Ripple can, and the code is already done and opensource.
then why don't we use it?
They're building the GUI for it right now (
https://bitcointalksearch.org/topic/holy-grail-bounty-225954). It's "usable," but is command-line only
how do you know? just taking their word for it?
I find it interesting how people will implicitly trust anyone who claims to be an open source developer. There is an assumption that there are no gain motives in these scenarios thus most rule out the possibility of deception.
ie. If someone is giving away something for free, why would they be lying about it?
I've posted elsewhere some of the statements of the project founder, and
copyright owner of OT. Let's just assume for a moment that there are no issues with the actual technology of OT(and there are), and just discuss the notion of licensing. What Chris Odom believes, is that anyone who modifies the OT code must check back in all their changes and publish them. This makes it virtually impossible to have a competitive business using OT, because all of your competitors have access to anything you might innovate. There is one party that is not subject to this rule, and that is Chris himself.
this concept is described here:
http://producingoss.com/en/dual-licensing.htmlan excerpt:
The problem is that any volunteer who makes a code contribution is now contributing to two distinct entities: the free version of the code and the proprietary version. While the contributor will be comfortable contributing to the free version, since that's the norm in open source projects, she may feel funny about contributing to someone else's semi-proprietary revenue stream. The awkwardness is exacerbated by the fact that in dual licensing, the copyright owner really needs to gather formal, signed copyright assignments from all contributors, in order to protect itself from a disgruntled contributor later claiming a percentage of royalties from the proprietary stream. The process of collecting these assignment papers means that contributors are starkly confronted with the fact that they are doing work that makes money for someone else.[emphasis mine.]
so technically, whoever contributes to this software project needs to also declare their copyright, and worse- anyone who uses it competitively must also gain permission from EVERY copyright owner(in theory, fact is these cases have rarely ever come up in court). So if anyone has contributed to this project, they also have a right to any profits gained from the licensing of this software. If what Chris claims is true, that there are MANY contributors to OT, then there also should be many Copyright owners(and this should be indicated in the software code).
So here, we are talking to the 'community' and what does that mean for us? Basically this makes building on top of OT pointless(and this isnt the only reason that's true), and anything you contribute to the project is, presumably, also under the same license and license owner(although this particular aspect is not clear and falls under the poorly defined 'derivative work'). Fact is GPL is not really amenable to business ideas:
http://www.linuxjournal.com/article/5935 . So if you want to do something profitable(personally I dont think you could do that with OT even if it were licensed MIT), you must rule out GPL licensed software.
Another good article about why GPL use is declining:
http://www.itworld.com/it-managementstrategy/233753/gpl-copyleft-use-declining-faster-everAslett is pointing to vendor use of community-based processes and governance (such as foundations) to hold projects together, rather than using the restrictive GPL licenses to be the glue the binds a project's development.
AGPL. is even MORE restrictive! http://en.wikipedia.org/wiki/Affero_General_Public_License
Basically it closes a known loophole in the GPL, that of using the software without modification(and not requiring publication) over a network(which will be in all cases if anyone ever manages to use this software to do something). Bitmessage for instance, is MIT licensed- it's based in sound concepts, it looks like an actual open source project.
So basically, this 'bounty' is an attempt by Chris Odom to get development done for free on his software platform. This is not the only suprise you get with OT but I'll save those for later.
Sorry if this doesn't read like a fun story out of Wired, but these are the nitty gritty facts of working in these areas.