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.
Nice. I was at first very confused about the support room chat, thought it was just a page to help you get started. Turns out it's a support chat for the app.
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 want to be competent.
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.
Sure, and I still use IRC every day. But IRC+emacs is going to be a tiny fraction of the world, saying "this product is useless because there is an advanced alternative" is like saying "Oh, why would anyone ever want to fly commercial, it's so much easier and more fun to build and fly your own airplane".
emacs was just my example, but there are tens of IRC clients, from web clients to GUIs to android apps. Everyone can find a client they can easily used.
btw, I recommend you change the code font-face order of
Monaco,Menlo,Consolas,"Courier New",monospace;
to
Menlo,Consolas,Monaco,"Courier New",monospace;
this way the nicer system-specific fonts will actually work, right now everything gets rendered in Monaco since it's universally available, and the nicer fonts are never used.
Also, maybe pick a more contrasting scheme for the syntax highlighting in code, right now it's very nearly indistinguishable from plaintext...
Are your chat logs encrypted and suitably protected? Losing your chat logs could be very damaging for a company - knowing that logs are safe is a required feature for us.
We're a team of five (two work remotely) at Citybot -- Lechat works very well for us. History is always there, no ridiculous kissing smiley faces (hello Skype), no ridiculous out of sync notifications that are months old (hello Skype). We've been beta testing it for about a month and it's been making our lives easier and communication clearer. The support is right on. The speed with which the Lechat team adds useful features is phenomenal. Never at expense of quality. Would love to see the native clients, and they say they're coming soon. I absolutely totally recommend it. Try it out!
Does this work with XMPP? Also, any chance of Pivotal Tracker integration? I've tried HipChat, Jaconda, Hall, Skype, etc... still trying to find something that works well for our team at Getaround.
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.
We have a distributed team of 4 engineers in 3 different locations. We have been using lechat.im for the last month and it has improved the information flow dramatically. Before lechat.im we tried hangouts, Skype and gTalk and those all fall short of the features that matter for a distributed team. Things that I love about lechat: search, SVN and git hooks (checking go into a separate room as messages), notifications, chat history.
We've been using lechat for the last few weeks and we are very happy with it. The UI is simple and clean. Fast history search is the killer feature for us. A number of nice UI details really show that this chat was developed by developers for developers.
46 comments
[ 2.5 ms ] story [ 102 ms ] threadGood luck! Hosted xmpp could be executed really well.
[1] http://prosody.im/
Very nice though.
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.
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.
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.
(edit: unless 2 co-founders are genuinely named Bob Smith and John Doe, in which case maybe consider changing your names :p)
Also, maybe pick a more contrasting scheme for the syntax highlighting in code, right now it's very nearly indistinguishable from plaintext...
Facebook took this approach with Facebook Chat but eventually offered XMPP. Curious to hear what value you think the native client approach would offer.
We'll link to it from the site soon.