Live data from Hacker News

Why Slack is inappropriate for open source communications

dave.cheney.net

211–220 of 536 posts

Re: Why Slack is inappropriate for open source communications

#211

Earlier quoted context omitted.

I just use Franz: http://meetfranz.com/

Two questions spring to mind that are not immediately obvious from the website - how do they get access to your messages in different accounts? Are they using some API? Or do they ask you for your username/password for each service and "helpfully" login for you?

It appears to be just a wrapper around web interfaces. Electron or some such nonsense. Truckloads of megabytes - binary size as well as memory consumption.

Re: Why Slack is inappropriate for open source communications

#212

Earlier quoted context omitted.

As a freelancer, I have EXACTLY this problem, so I started hacking away on my own solution. Don't want to shamelessly promote myself here, but if you're interested, link is in my profile.

A few comments that I hope are constructive. Looking at your page, I'm not confident you're avoiding the issue by which these tools proliferate: https://xkcd.com/927/ Your users and their clients are still going to be using Slack and email, but it seems like you're giving me one more thing to log into. You write: > Schedule your time spent and group distracting reminders and notifications in one place If this "one pl…

Aka Trillian from the last Great Messenger Client War.

Re: Why Slack is inappropriate for open source communications

#213
A great alternative to Slack, in the spirit of IRC, is matrix[1]. It has lots of clients, and a great vision.

You use an online client called riot[2] which uses the matrix protocol. There are other clients available[3] including desktop clients.

There's E2E encryption coming to more of the clients which is inspired from signal protocol (double ratchet part of it specifically), without Forward secrecy so as to maintain session history on new devices.

I think it has a bright future and you should consider it too.

[1]:https://matrix.org

[2]:https://riot.im

[3]:https://matrix.org/docs/projects/try-matrix-now.html

Re: Why Slack is inappropriate for open source communications

#214

I feel like more and more people are coming around to seeing the relevancy of distributed federated chat and breaking out of the walled gardens. My person money is on Matrix[0] taking off but I think the general theme of people pulling away from interesting their communication to corporations is a positive. [0] matrix.org

Similarly, the huge buzz over the past few weeks about Mastodon as a distributed/decentralized micro-blogging service has been positive. People starting to learn more about federation and decentralization. Good to see.

Re: Why Slack is inappropriate for open source communications

#215
post #212

Earlier quoted context omitted.

A few comments that I hope are constructive. Looking at your page, I'm not confident you're avoiding the issue by which these tools proliferate: https://xkcd.com/927/ Your users and their clients are still going to be using Slack and email, but it seems like you're giving me one more thing to log into. You write: > Schedule your time spent and group distracting reminders and notifications in one place If this "one pl…

Aka Trillian from the last Great Messenger Client War.

Well, perhaps but I am more trying to develop a service to avoid the Slacks and Basecamps of the world, while still being aware of what's going on, rather than just being a multi-network client.

Re: Why Slack is inappropriate for open source communications

#217
I personally prefer Gitter & other tools over Slack for open source communications. The Slack signup process can be a road block as it takes to many steps. To often I run into open source communities that require you to join their Slack channel for posting any questions (that may or may not be bugs in their software).

I really like Slack for a lot of things, but it's often a tool used incorrectly due to its popularity.

Re: Why Slack is inappropriate for open source communications

#218
post #133

Earlier quoted context omitted.

If it's anything like my experience, the trip from clicking on the button to open the app and wait for the myriad of redirects, before clicking through to the page you actually want to monitor is non-trivial (and sometimes doesn't occur if the tab isn't in the foreground). I don't have that many open, and it still takes me around 5 minutes every day to open them back up.

At least you have SSO! Imagine what if you had different credentials to each of these services (even logins)! There are big companies that operate like that...

Install 1Password and it's basically like having SSO.

Re: Why Slack is inappropriate for open source communications

#219

Earlier quoted context omitted.

What is Lounge missing compared to IRCCloud?

Mobile. And other projects, including the GPL project Quassel, do have mobile clients (although Quasseldroid, which I maintain, isn’t exactly the best client in the world).

Lounge has a responsive view you can save to home screen on iOS and android. Looks like this: http://i.imgur.com/MmajSU1.jpg

Re: Why Slack is inappropriate for open source communications

#220

I can't believe that in 2017 we're still discussing what's wrong with our chat software. I have to wonder when we will finally see chat as a solved problem.

The OP isn't actually discussing chat as an unsolved problem. OP is arguing that chat is the wrong choice of solution to the problem of open source software project communication, because it's synchronous.

Or to abuse a metaphor, OP is arguing we need to use boats instead of cars to ship heavy things overseas, not that cars are an unsolved problem.

Post reply on HN