yet another renaming
====================
(sorry)
* sephiroth: channel
	(currently "sephiroth" the program also contains:)
* jenova: database server, meeting point
	(needs to be split off)



* who response: {id nick login-epoch idle-time mode status}
["LAG2" "Robey" 904939939 35 "away" "making whoopee"]
~128 bytes per response max
limit to 20 users
members-verbose: { count:12 fields:[ "id" "nick" "login-epoch" "idle-time" "mode" "status" ]
        users:[ ["LAG2" "Robey" 904938299 34 "away" "making whoopee" ] [...] ] }

...no, do it state-fully:
begin-response:{ count:12 response:"members-verbose" }
members-verbose:{ id:"Robey" nick:"yebor" ... }
members-verbose:{ ... }
    ...
end-response


* client should have an ip/port field where other clients can reach
  them for private convos

* sephi needs some way to verify that a nick change on a channel won't conflict with a
  user in jenova's database.  this is a policy decision by sephi (he doesn't HAVE to
  ask, but he ought to have the ABILITY to ask if he wants to avoid nick-id conflicts)

* how to create a new account?

* reconnecting to the sql server might take more than 5 minutes *poof*



current records:
* bastille.lag.net had 136 logins for an uptime of over 28 days,
  using sephiroth/0.2, ending on 14 dec 2000

