Usernames are case insensitive and can contain any character.
Urls can have port numbers and paths attached.
**@genjix@** rules@fishysnax.com:443/path/to/
That's a valid address. The username = "**@genjix@** rules"
Now the URL is called using some remote methods like url + path + '/getaddress/' so that the implementation is non-specific to PHP. Anybody is free to create their own specific implementation with their own server policy. The current policy happens to be very simple (update record, set password, get address).
Like a user who wanted to setup their own private provider could setup an implementation on their server and disable creation of new accounts.
Obviously I want to get something in there with PK crypto... But haven't come up with a properly secure scheme yet. Many of them are prone to MITM attacks. However this can be used for small amounts effectively like a post on irc for somebody to send you X BTC to
genjix@foo.org without having to open bitcoin.
There's 2 class of queries- the public fetch record (uses GET) and the 2 calls to change things and require a password (and hopefully more security in the future- uses POST).
The POST queries return a JSON. If there's a key by the name of "status" then it was successful and the value will give you an update as to what occured. If there's a key called "error" then it was unsuccessful and the value is an error message. The JSONs can also have other entries depending.
