131–140 of 285 posts
Earlier quoted context omitted.
Chat is just nicer to work with. Emails are in their own isolated packages. If i get an email saying the build broke, there is no easy way to check the last time it happened. I wouldn't be able to glance at the last few messages and see that the build breaks every time "X" commits or the tests fail every monday. I can't easily get context on what someone was doing when it broke. With something like slack it's all rig…
I would just create a folder and a mail rule that moves the mail automatically. You would actually be able to filter your mail with more granularity than what a simple Slack channel can provide
Earlier quoted context omitted.
That doesn't sound so much as Skype being good as VOIP being good too you. Skype itself in my experience, and all those I know, has been abhorrent. Chat messages appearing out of order and once literally months later, incorrect status indicators, automatic noise cancelling messes up the volume sometimes (it seems to happen when the signal/noise plummets for a bit) forcing you to recall to get usable audio levels agai…
I remember performing the periodic AppData cleanup in 2009/2010 but haven't had to do that in the last few years. It was during that time that the chat delay issues were very common as well. From my point of view, while the Microsoft takeover and remake initially brought difficulties with login, the recent versions were not too bad apart from the Windows 8 Store version mess. But that is just my experience. While I p…
I would be a fan of Skype, if they did not route everything through government spyware.
While I'm not sure that's what they do they DID get caught red-handed a couple of years ago snooping on urls sent over Skype.
Earlier quoted context omitted.
While I'm not sure that's what they do they DID get caught red-handed a couple of years ago snooping on urls sent over Skype.
"route everything through government surveillance" is perhaps a bit too blunt, but let's not forget that Microsoft was the founding member of the PRISM program. And Prism or no Prism-- Skype was a $1bn present from Microsoft to the intelligence community. Even if they never snooped on anything (we know they have) they did re-engineer skype in a manner that allows it to be subject to more traditional CALEA trap and tr…
Earlier quoted context omitted.
>it's unfathomable how Slack could still not have this feature I hear this saying a lot, and every time I just can't take it seriously. This is the first time I've ever heard of someone wanting customizable background colors for messages on a messaging platform. It's just not something I or anyone I know about cares about. I just can't see how that would be considered a high importance feature by anyone.
People go ape-shit about silly features in IM clients all the time. Case in point, emoticons
We initially used Skype on our team to communicate with others. However, the software was horribly buggy on OSX. Slack has become part of our main toolchain. It works, has the basic features you need and doesn't get in our way. The integrations are great and we'll continue to use them. Unless Microsoft rebuilds Skype for the ground up, I don't see us leaving Slack for it. They had their chance, and they dropped the b…
This. This exactly. Is it really unbelievable to assume Microsoft wouldn't attempt to build their own IRC+ clone and save a few billion while they are at it?
I do agree with you, Slack is much better than Skype, but I would add that Lync is just as good. I went from Lync to Slack (after changing jobs) and I would say that Lync not only works just as well but has more features a team would find useful. For instance, multi-user video+voice chat w/ great screensharing/presentation functionality.
Edit: Should mention I was using Lync in a Windows shop and now Slack in OSX. In Windows it worked perfectly but I could be convinced it had issues in OSX.
Most acquisitions by big businesses, either early or late stage, destroy value. Big biz thinks they can innovate by buying. Smaller biz wants an exit. The innovation exits on acquisition and after earn-out. Both suffer and we all lose what could have been the next Google.
Earlier quoted context omitted.
>get eclipsed every 5-10 years as a new generation comes along with a new favorite tool I wonder if this rule holds just as much for IRC - for most FOSS projects, IRC is the go-to choice, and it's been that way for a long time.
IRC is my favorite, but IRC is bad for company, because you have to manage your own IRC server (you don't want to host your company stuff on freenode, do you). Also, IRC doesn't come with any integration with third party tools. Unless you have a very willing hacker willing to build the integration from scratch, IRC is bad. Not that you would never find a use case to write custom bot on Slack for your need, but I imag…
There is a hurdle here, but it's not so bad if you're already willing to run your own IRC server. I wrote nodebot[0] to allow machines and scripts to send messages to IRC, it would be a day or so to put an HTTP request handler (apache with a CGI even) in front of this, slap some TLS and http auth on that URL, and expose a webhook that these external services could hit.
One of the great things about slack is that many integrations already exist, so it's often just a matter of sharing an API key or some other credentials between the services, and anyone can do that. I do, however, run into issues with things like github which has many outgoing integrations with services that also use github's incoming API. It can quickly become a mess -- where should the authority lie for doing integrations: with the chat app or with the individual services?