HipChat releases native app for Mac
121–129 of 129 posts
Re: HipChat releases native app for Mac
#122Re: HipChat releases native app for Mac
#123Re: HipChat releases native app for Mac
#124Earlier quoted context omitted.
What happens when ec2 shuts down the machine with jabber on it? When there's a memory spike in the middle of your vacation and no-one can send messages? Etc, etc, etc
You turn the machine back on? Switch to a server provider that doesn't randomly shut your machines down? What do you do when hipchat's severs are down? Twiddle your thumbs and wait for it to magically come back? At least if it's your server you can actively fix it instead of waiting for someone else to do it…
Re: HipChat releases native app for Mac
#125Earlier quoted context omitted.
One major difference is that it maintains persistent state - so when I log back in I see all the history and conversations from when I was logged out.
I've never really had a thorough introduction to IRC. Is it correct to assume that it's 100% ephemeral, that all conversations, questions, answers are gone when you log out? If that's the case, I'm puzzled as to why it would maintain so much traction when the record of communication can be so valuable (e.g. people searching the log vs asking a question that has been answered many times... )
The server module which actually connects to, and interacts with, the IRC server.
The client portion which connects to, and interacts with, the quassel server.
Most people just use "Quassel" as a simple desktop app in which case both modules are merged and it acts just like a normal IRC client.
However you can also install the server module on a server somewhere in which case it stays connected to the IRC server, buffering chats etc. You can then connect to it with the client part of quassel which is installed on your local desktop, which you close it all you are doing is closing the client module.
I really like that design, a good separation of concerns allows it.
Re: HipChat releases native app for Mac
#126Earlier quoted context omitted.
at that point you might as well get google apps for business.
Google doesn't exactly have an "IRC on crack" product though? Also, I find GTalk's routing to be spotty when it comes to multiple devices - it's quite common for me to receive messages from coworkers at night and have them route to my work machine instead of one that's active on the GTalk account at home. Nowadays we use GroupMe for things that must be read in a timely manner. It'd be nice if we could use GTalk for i…
Re: HipChat releases native app for Mac
#127I know people are happy as the infamous GIF bug is fixed, but seriously this is one of the worst 'beta' apps I have tried. This mac app has been in development for ages, then been in closed beta and now finally it's available to everyone to try. Our team just switched to the beta native app, and already found several critical bugs with the app within minutes. Sorry guys, this is really poorly put together and the num…
I'm on the most recent OSX version in case this might make a difference. No bugs or crashes for me so far.
Re: HipChat releases native app for Mac
#128Earlier quoted context omitted.
I've never really had a thorough introduction to IRC. Is it correct to assume that it's 100% ephemeral, that all conversations, questions, answers are gone when you log out? If that's the case, I'm puzzled as to why it would maintain so much traction when the record of communication can be so valuable (e.g. people searching the log vs asking a question that has been answered many times... )
The Quassel IRC client is actually split into two pieces. The server module which actually connects to, and interacts with, the IRC server. The client portion which connects to, and interacts with, the quassel server. Most people just use "Quassel" as a simple desktop app in which case both modules are merged and it acts just like a normal IRC client. However you can also install the server module on a server somewhe…
I may be wrong, but I feel like the right persistent chat service can/should become a 21st century usenet/google group, where the conversation is always happening, IFFT-style hooks help you filter/act on info, and history is Gmail-simple.
I'm investigating a group-chat solution right now for an organization of several thousand non-technical members, and my intuition tells me IRC would simply not be adopted by most users.