http://risovach.ru/upload/2016/03/mem/novyy--shablon_1085837...
Open Sourcers Race to Build Better Versions of Slack
41–50 of 397 posts
Re: Open Sourcers Race to Build Better Versions of Slack
#42Earlier quoted context omitted.
Doesn't mention IRC, doesn't mention Discord. I'm suspicious that a PR firm pushed this to a journalist.
This and the number of apologists seems a little suspicious indeed.
Re: Open Sourcers Race to Build Better Versions of Slack
#43This 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, expand…
Revolution? Drinking the kool aid much? My team has it. We've had it for a month or two now. There has only been a handful of posts and most of them are "TGIF" posts.
As you can tell from my post which states that Slack doesn't offer anything unique or special, uh, no, I'm not drinking the kool-aid.
Re: Open Sourcers Race to Build Better Versions of Slack
#44Earlier quoted context omitted.
Doesn't mention IRC, doesn't mention Discord. I'm suspicious that a PR firm pushed this to a journalist.
This and the number of apologists seems a little suspicious indeed.
Re: Open Sourcers Race to Build Better Versions of Slack
#45If 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 sui…
Re: Open Sourcers Race to Build Better Versions of Slack
#46One thing that nobody's mentioned yet is encryption. A Slack alternative that's end-to-end encrypted (at least for private messaging between users) and has encryption for chatrooms would be worth my time.
Re: Open Sourcers Race to Build Better Versions of Slack
#47One thing that nobody's mentioned yet is encryption. A Slack alternative that's end-to-end encrypted (at least for private messaging between users) and has encryption for chatrooms would be worth my time.
Re: Open Sourcers Race to Build Better Versions of Slack
#48I was blown away on how much better the UX was in Gitter compared to IRC. The history, the notifications, the markup, the UI...you name it.
And Gitter is a pretty crappy client. If there was a nicely implemented client, it would be even more impressive.
Re: Open Sourcers Race to Build Better Versions of Slack
#49Earlier quoted context omitted.
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…
Messages just like that show up in Slack whenever someone joins or parts the channel, changes the topic, etc. Not sure this is a valid complaint.
It doesn't help that IRC tends to get used in places where massive amounts of users are expected. I feel some of the newbie clients should just hide by default join/quit spam.
Re: Open Sourcers Race to Build Better Versions of Slack
#50For talking about a race, Wired seems to have neglected a crucial technology: ircv3[1]. I'm not very fond of IRCv2, and have moved away from it where I previously used IRC. But IRC is popular, has a lot of clients, and v3 has a lot of promise. Why didn't the author bother to mention it? [1]: http://ircv3.net/