But you're chat for developers! You're never going to be able to offer the level of customization people get out of Adium/Messages/their chat client of choice.
Facebook took this approach with Facebook Chat but eventually offered XMPP. Curious to hear what value you think the native client approach would offer.
I can search an emacs IRC buffer (it's just like searching a text file) or if I want to search everything I can just grep in my logs directory and get search results in emacs which I can then grep some more or easily copy paste to another buffer where I have a file open or a colleague who I'm chatting with.
For multiple windows, I can split my emacs in however many windows I want horizontally and vertically and switch around with whatever key bindings I want.
The finance team at appnexus use ipython internally to scrape files, create aggregates, etc.
I dunno, it's just about teaching them about it at the right level. Don't swamp them with thousands of details, and don't leave them without a lifeline to call upon.
Although this is assuming they are a bit open-minded.
The finance team at appnexus use ipython internally to scrape files, create aggregates, etc.
I dunno, it's just about teaching them about it at the right level. Don't swamp them with thousands of details, and don't leave them without a lifeline to call upon.
Although this is assuming they want to be competent.
Neat. My friends and I switched from ejabberd to Prosody[1], a Lua XMPP server; Lua is quite a bit easier to use than Erlang (unless you are already an Erlang grandwizard), so writing new plugins is a breeze with prosody. Of course, ejabberd already has a lot of plugins written, so lots of benefits there as well.
Good luck! Hosted xmpp could be executed really well.
