Live data from Hacker News

Open Sourcers Race to Build Better Versions of Slack

wired.com

11–20 of 397 posts

Re: Open Sourcers Race to Build Better Versions of Slack

#11
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

Every time Slack is mentioned here someone brings this up. I can't help but think they've missed the point. User experience is important.

Re: Open Sourcers Race to Build Better Versions of Slack

#12
Hopefully Mattermost and Rocket.Chat both build mature, robust HA systems since their features [honestly] are on par with Slack. Then move into SaaS hosting of their service in VM clusters across ~3 regions. :)

Really, the only thing that stops me from wanting to use these services at $DayJob is the fact I have enough stuff I have to maintain. I'd really rather just pay $99/month for a 10-20 person team.

Re: Open Sourcers Race to Build Better Versions of Slack

#13
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

Slack is IRC, it just is a really nice interface that makes it easy to automate and makes it easy to share files/code/etc.

That's Slack's main feature. Well that and gifs. IRC on the other hand is James has left the channel. Bill has left the channel. Samantha has joined the channel. Samantha has left the channel. filled with worthless status updates Martha has gone idle that make it Bill has joined the channel. terribly easy to Bill has changed the channel topic to "ZOMG! Ponies!" miss things Martha has become active Martha has left the channel.

Re: Open Sourcers Race to Build Better Versions of Slack

#14
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

This comes up every time, and as usual you have totally missed the point.

IRC is difficult to configure, difficult to host, difficult to use, and does not offer the same feature set as Slack. There is an obvious use case for something like Slack (obviously, because otherwise it would not have millions of users!) and covering one's ears while yelling "IRC! IRC! IRC!" is sort of wilfully ignoring that if it were a suitable solution, Slack would never have taken off.

Re: Open Sourcers Race to Build Better Versions of Slack

#15

It's good to see a bit of a variety – we all know that monoculture ends up being a bad thing, and there are obvious downsides to applications hosted by third parties (though of course in some cases it's not a problem!). Of course, there's no real network effect with applications like this either (beyond integrations support) so there's a relatively low bar to switching when compared to something like Facebook. I do h…

Mattermost claims to have "Native Applications". (http://www.mattermost.org/community-applications/#native)

Turns out they mean "electron is a native application, and our app is a webpage inside of electron, so our webpage is a native application."

Bummer. I use both Slack and Hipchat for different groups, and I'm not happy with the wrapped webapp for either of them.

Re: Open Sourcers Race to Build Better Versions of Slack

#16
This is one of those applications that is always being rewritten somewhere. JWZ's law may even be relevant here: "Every program expands until it reads mail". It seems there is always a large group people out there working on messengers.

The question really is what made Slack special. Why is it the Slack revolution and not the HipChat revolution? What about the veneer has allowed it to become a pervasive trend, expanding into non-tech companies and being hailed as a permanent replacement for most emails? This is the only interesting question around Slack, since, as numerous other commenters have pointed out, it doesn't really bring anything to the table that the messaging space hasn't seen a good number of times before.

Re: Open Sourcers Race to Build Better Versions of Slack

#17
post #7
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

if only getting external collaborators or non-technical users into IRC didn't involve sending them a 15-step howto on configuring screen and ssh and could be as simple as "check your email and click the link you get" and, if only there was push button per channel access control set up out of the box so that some users can join some channels but not others! no, not channel keys, those are busted (what do we do when so…

Your experience of IRC clients seems like a bad one, I'm sorry about that.

Have you heard of irccloud.com? You should check it out. My mum could use it (I'm not affiliated with them in any way besides being a happy customer).

Re: Open Sourcers Race to Build Better Versions of Slack

#18
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

Design counts. Execution of that design counts. User Experience counts.

Re: Open Sourcers Race to Build Better Versions of Slack

#19
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

Offline messages with IRC is a bit of a pain to set up and scale easily.

Re: Open Sourcers Race to Build Better Versions of Slack

#20
post #2

If only there was a well supported, standard, open and interoperable text messaging protocol (with multiple implementations) that companies could host themselves... Oh wait, IRC.

Doesn't mention IRC, doesn't mention Discord. I'm suspicious that a PR firm pushed this to a journalist.
Post reply on HN