1. Why isn't the server opensourced yet.
As soon as the network is distributed, changes can only be made by consensus. By intentional design, logic changes are difficult to do and require establishing and maintaining a consensus on the change. You wouldn't want someone quickly pushing through a change that, for example, allowed issuers to delete IOUs!
Right now, Opencoin is acting as a central authority and running the network. This makes it much easier to fix problems and make changes quickly. We're fixing issues on a daily basis now and slowing that pace would mean a much longer time before Ripple is a decentralized payment system that people can truly rely upon.
2. Do you really expect people to make a list of person they trust or person they don't?
Not any time soon. That's why we're promoting Ripple as a payment network with gateways rather than as a community credit network. I personally believe that community credit is Ripple's long-term killer app and that it will change the way people think about money. So this will always be there and maybe one day it will really catch on. Social money may take social changes, just like social media did. Those changes happened pretty fast, so maybe these will too. It will take better tools to make managing credit more user friendly. We hope to get there, but we aren't relying on it happening soon. The bigger Ripple becomes, the higher the chances this will happen.
3. Paying still requires a user unfriendly address like: rKXFsg5EuG4BzLxdTBFXJq2a6iNfyx1hRX Is there any plan to make it friendlier? (like allowing to send money to an email address by allowing people to make an alias?)
Yes, however, we've run into some technical problems designing a usable and safe namespace scheme. The fundamental problem is not having a central authority that approves names but also not having the first person to register names like eBay and Amazon being able to hold them hostage.
The best solution we could come up with is this:
1) Anyone can create a namespace.
2) The client can use any namespace.
3) Opencoin will create a namespace which the client uses by default.
4) Namespaces can be closed or open. They start closed. A namespace's owner can open a namespace but not close it.
5) Opencoin's namespace will be closed for a year or so. We'll come up with some fair scheme to register names. (Yuck.)
6) After a year, we'll open our namespace and it will be first come, first served.
The problem is that this is kind of fake decentralization. If someone tries to create a competing namespace, payments may go to the wrong person. So as a practical matter, we'll run the namespace, and we don't want to do that. We don't want to be Ripple's IANA.
We have a hard rule that we won't implement something until we find a good way to decentralize it. We're not there yet on friendly names.
We do have a domain-based naming scheme because that can be decentralized. Domains can vouch for their ownership of particular account records. You retrieve a domain's configuration file using SSL.
For example, this is bitstamp's main account:
"account_data" : {
"Account" : "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
"Balance" : "177780471670",
"Domain" : "6269747374616D702E6E6574",
"EmailHash" : "5B33B93C7FFE384D53450FC666BB11FB",
"Flags" : 131072,
"LedgerEntryType" : "AccountRoot",
"OwnerCount" : 0,
"PreviousTxnID" : "8E64754BE835889A4DB2E1940FD460977EEAAD5A7BC2DC8EFD74E9C4150DC53D",
"PreviousTxnLgrSeq" : 282734,
"Sequence" : 34,
"TransferRate" : 1002000000,
"UrlGravatar" : "
http://www.gravatar.com/avatar/5b33b93c7ffe384d53450fc666bb11fb",
"index" : "B7D526FDDF9E3B3F95C3DC97C353065B0482302500BBB8051A5C090B596C6133"
}
Notice the "Domain" field? That's hex for "bitstamp.net". If you retrieve
https://bistamp.net/ripple.txt, you get:
[accounts]
rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B
[hotwallets]
rrpNnNLKrartuEqfJGpqyDwPj1AFPg9vn1
[domain]
bitstamp.net
This establishes a reliable proof that the domain belongs to the "bitstamp.net" domain.