Hey there, road warrior!

Hello there! Yes, I'm afraid I'm still cut off to a large extent from the
net, and as such can't do much development. However, over the past few
days I have been indulging in a little development as a reward for having
finished and submitted my UCAS form, so I now present to you:

(1) EB-RPC. This is an XML-RPC proxy server, which allows Everybuddy
connections to be carried over HTTP (for example, to get through a proxy
server to a core hosted outside). The RPC protocol is documented in
misc/eb-rpc/doc in subversion, but the version there is out of date and
the sample client-side proxy (which talks the normal TCP to the interface
and XML-RPC to the proxy) isn't in the repository. I'll update the
repository when I get back online. There is, however, a copy of the server
running at http://www.everybuddy.com:8081/ for anyone who wishes to roll
their own client (or is sufficiently interested to ask for a copy of mine
- I'll email to anyone who really wants it).

(2) RoadBuddy, which is about to undergo a new alpha. To download the
latest version, point the WAP browser on your Java-enabled mobile phone to
http://www.everybuddy.com/index.wml and follow the "Download" link. The
client/server interaction protocol has been revamped - once again, I'm
afraid it's not in subversion yet, but there's a copy running at
http://www.everybuddy.com:8080/RoadBuddy (the default option).

(3) WebBuddy, a brand spanking new HTML interface. Currently supports
status setting, away messages, and conversation. Lacks contact/account
management, actions and group chat, so you'll need another interface to
set up your core before you can use WebBuddy. Another victim of my network
connection, this is currently only available as the running demo at
http://www.everybuddy.com:8080/WebBuddy/servlet/Login

Please note that although there are running copies of all of the above on
everybuddy.com, that does NOT include the core - you'll have to supply
your own, accessible from anywhere on the Internet, for that...

...which brings me neatly onto my next topic. I have been considering a
hosted core scheme. The idea is that someone would sign up, possibly pay a
nominal hire fee to cover the extra bandwidth once we go beta, and get
their own Everybuddy core, hosted at shell.lazzurs.net. They could then
connect to it from wherever they were on the Internet, even in situations
where they couldn't run a user interface (just use WebBuddy!), or from
their mobile (using RoadBuddy). What's more, they could stay permanently
connected with an away message, so that people could find out where they
are no matter what (ever wanted to pin an "I'm in a meeting, catch me at
2:30" sign on their virtual desk?) . People could then leave messages
which would be picked up the next time they connect. I already operate
something like this for myself, and have constructed a set of scripts to
maintain any number of cores running simultaneously.

So, is anyone interested in testing this concept out? No question of
payment while the service is patchy and alpha-ish, of course - I'd just
like to see how plausible this is. Please tell me what you think!

Meredydd