Thanks for your help, folks, and I'll look into that tutorial.
I'm going to continue to play with SwiftRiver out of personal interest, but I've gotten a separate message from someone from Ushahidi, indicating that because of the $500 cost of "the Twitter firehose", the project as a standalone thing was essentially abandoned as being too costly for anyone to use.
I have to admit, I'm not really sure I understand this: I'd imagined that this wasn't vastly different than using the Twitter API, and a synthetic Twitter ID perhaps, to follow certain other IDs and do searches. I don't really know much about the Twitter API at the moment, other than having set up the conduit "app" for Ushahidi. I suppose I'll have to learn a little more. Any enlightenment on this would be appreciated...
(This should be a simple problem, though, right? Unless authentication is Just Plain Broken in v1.0, or I've bobbled something, then I should be able to plug in a row in the users database with the correct values and get in, right? So what's the 512-bit MD5 hash for "password" or some other Well Known Value...? Hm. An Approach, perhaps.)
Anyway, it's something of a moot point now, since this "hackathon" has now ended, victory has been declared. Unfrotunately, I haven't seen any actual evidence of any of this hitting the ground or assisting a single person or organization actually working in the Philippines right now.
I sent out detailed documentation on the Ushahidi as it stood very late last Tuesday (or early Wednesday) in response to this "request from the President's" etc., etc., and have never received any response, not so much as an acknowledgement.
While I was waiting the organizers pressed me to do what amount to busy work — e.g. putting up a "microsite" dedicated to solving the same problem I'd already solved with the Ushahidi, despite the total lack of evidence that anyone in the Philippines had actually looked at the site.
One of the program managers also shared with me a story about someone from Doctors Without Frontiers "finding" the site — a site which had no domain name associated with it at the time, just running off a naked IP address — and being "disappointed" to find no medical information on there. When I pointed out the complete unlikelihood of this, especially considering that my actual email address is right on the home page of the site and no one from DWF had gotten in touch with _me_, he admitted that he'd "misspoken".
I've come to the conclusion that this was essentially an ill-thought-out publicity stunt — it did, in fact, get them two quite breathless articles in TechCrunch — no one involved seemed to have either meaningful contacts in the Philippines nor any previous experience with a disaster relief and recovery situation.
Many of the projects were extremely unrealistic — projects predicated on the possession of a smart phone and a working Internet connection when the Philippines has the lowest penetration of smart phone ownership in the entire Asian region, for example.
A learning experience to be sure. Sites like Tomnod did a great job of harnessing the "power of the crowd" to do stuff like identify different kinds of damage on satellite imagery; others classified tweets. That worked _great_. Harnessing the power of a crowd of developers? Not so much.
Seems like crowd-sourcing is a lot better for tightly constrained gruntwork than actual development and deployment of complex software in a complex situation. Live 'n' learn.
Thanks for the help!