Hey all!
I've been a bit quiet lately getting a bunch of projects caught up,
various of which I'll be posting about in more detail.
One that I'm really excited about is getting the import side of our
Twitter bridge fixed up so it can run on large sites (identi.ca) or a
large number of small sites (*.status.net hosting).
Twitter's streaming APIs are stabilizing, and it looks like we'll be
able to use a limited number of persistent connections to listen for
many users' timeline updates at once, without ongoing polling or
expensive per-site processes.
I've written up some notes for those who want far too much detail:
http://status.net/wiki/Twitter_bridge
My work branch so far is able to run a single user's import via the User
Stream API subset:
http://www.gitorious.org/statusnet/brion-fixes
Pull URL: git://gitorious.org/~brion/statusnet/brion-fixes.git
Branch: twitstream
This should extend relatively cleanly to multi-user Site Streams, at
which point the 'hard part' is connection management and filling in
holes from when the daemons are down. :)
-- brion vibber (brion @ status.net)
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
