neat. Can I be the first to recommend that you peruse the federation specs (OStatus/Tent.io, also there is a w3 working group mailing list http://www.w3.org/community/fedsocweb/) and try to solve the silo/walled garden issue?
to elaborate, I think there is a huge future in what I call Status Update Services, and I think the trend will be for organizations to move away from the incumbent service providers towards infrastructure under their own control (as in the e-mail model.)
We're working on supporting multiple auth providers, but the larger question of federation is more interesting, and equally harder. We're not sure about where to take Firefeed yet, since it was built as a demo for Firebase, but that's something we'll definitely consider in the future.
Cool, happy I'm giving helpful feedback. The field is just starting to take off, but I think it's great that there is now a growing selection of small message/status update/microblog software.
It's possible that government agencies, universities, businesses, etc can take advantage of running status update services, which can be made either be public or private, tied to their own domain/network, and maintain administration of user accounts. Many other advantages from having this sort of infrastructure develop will be seen as well.
to elaborate, I think there is a huge future in what I call Status Update Services, and I think the trend will be for organizations to move away from the incumbent service providers towards infrastructure under their own control (as in the e-mail model.)