Slack client for the terminal • Hacker News Board

Re: Slack client for the terminal

#181

Post by bphogan » Wed, Mar 07, 2018, 6:13 AM UTC

rspeer wrote: post #160

bphogan wrote: post #127

Earlier quoted context omitted.

Disagree about barrier to entry. I run an office hours chat for my online classes powered by IRC. I use KiwiIRC as the front-end. Students need only the web address of the web page I want them to go to. When they get there, they need only a username. No signup, no verification, none of that. They're online, getting help in seconds. Individual public channels requiring nickserv registration and all that? that's anothe…

> cherryh.freenode.net set mode +ns ##irc_can_be_easy Some welcome message. You may be too used to IRC to recognize this, but this is frightening gibberish to 99.99% of computer users. Also, this interface does not get you crucial features provided by other chat services, such as seeing what previous users have said.

IRC is an open protocol. Messages like what you see can be hidden by the client or suppressed by the server. And free intermediary servers can keep logs.

It's amazing to me how people think Slack is this amazing tool. If someone had thrown millions of dollars at IRC, it wouldn't suck.

But instead, you'll fork over your personal info and insist I do too.

Re: Slack client for the terminal

#182

Post by rockostrich » Wed, Mar 07, 2018, 2:21 PM UTC

rekoros wrote: post #104

rockostrich wrote: post #97

Earlier quoted context omitted.

Hipchat, Facebook's Workplace, and whatever Microsoft's service is are all competitors but I don't think any of them are serious. Hipchat is probably the biggest competitor, but that's because it was around before Slack. When there's a serious competitor in the space, then I'm sure they'll start caring. For now, I don't think anything else is close.

https://hipchat.com

Hipchat was the first one that I mentioned...

Re: Slack client for the terminal

#183

Post by rekoros » Wed, Mar 07, 2018, 2:50 PM UTC

rockostrich wrote: post #182

rekoros wrote: post #104

Earlier quoted context omitted.

https://hipchat.com

Hipchat was the first one that I mentioned...

I know!

I’m inviting you to navigate to its website, to see what happens there :-)

Re: Slack client for the terminal

#184

Post by sRabbit » Wed, Mar 07, 2018, 7:25 PM UTC

qudat wrote: post #148

NikolaeVarius wrote: post #9

I use this personally. Its great. Hides all the cruft that people post in slack as text. I've been working on trying to extend it on the side. A chat client should not be taking over 1GB of RAM

> A chat client should not be taking over 1GB of RAM Why do you care so much about RAM usage? All this concern over RAM is completely missing the picture here. Every conversation about slack or electron people complain about RAM usage. The market could not give two shits about RAM usage so why does everyone on HN complain about it?

Because when you combine that with the silly MS overhead from useless processes because the team that controls your Win 10 environment insists on running Group Policy without a care.. then you notice that your machine is suddenly bogged down, when it's been running fine for the years you had total control of it! !!