Live data from Hacker News

Please don't use Slack for FOSS projects (2015)

drewdevault.com

61–70 of 136 posts

Re: Please don't use Slack for FOSS projects (2015)

#61
post #29

The biggest problem for me in IRC is lack of good mobile clients. You can't get push notifications and if you want to stay persistently online then you need to keep a perpetual battery-draining socket open. You could setup a relay on your server ,but it's cumbersome and too technical for most people.

I use ZNC with the znc-push module. It supports a ton of different services, but I use it with Pushover. Notifications come in on time even when my phone is deep sleep.

As for my mobile app, I use an app called Palaver on my iPhone.

Re: Please don't use Slack for FOSS projects (2015)

#62
I do like IRCCloud, and use it often. But it's not Slack. Slack is one of those things that seems sortof dumb and simple but it just isn't. They've built a very compelling set of features that many of us now just take for granted. Mattermost is the closest 'freemium' alternative to Slack I've seen.

Re: Please don't use Slack for FOSS projects (2015)

#63
post #34

Earlier quoted context omitted.

That's not necessarily true. If you're a certified non-profit, you can get free Slack with unlimited message history for up to 250 users ( https://slack.com/help/articles/204368833 ).

Interesting, I didn't know about that. What happens if you get 251 users though? EDIT: Answered my own question: up to 85% discount, which is very nice, but still might be infeasible for many projects/communities.

> Answered my own question: up to 85% discount

Isn't Slack's cheapest plan around 8$ per user per month?

Re: Please don't use Slack for FOSS projects (2015)

#64

My only issue with IRC as the alternative to Slack is that its really user hostile. Clients largely look like some 90s programmer’s idea of a chat tool, and as discussed, persistence and sharing files and things are extensions or hacks on top of the protocol. Without addressing these, IRC is going to remain the ‘underground’ tool it is at the moment, with little support from enterprise tools and other integration pro…

There are several richer IRC clients; the author of this article suggests https://thelounge.chat/ in a later article about IRC.

Re: Please don't use Slack for FOSS projects (2015)

#65

Earlier quoted context omitted.

Many projects prefer a limited history for interactive chats.

https://en.m.wikipedia.org/wiki/The_Fox_and_the_Grapes

I think it’s a bit snide and snarky to just post a link like that.

And I don’t even think it’s applicable - in the community I’m in we decided we didn’t want an eternal log of everyone’s discussions. More formal discussions in PRs and emails are recorded, but we rather let conversations fade away after some time.

Re: Please don't use Slack for FOSS projects (2015)

#66

Acting like IRC is equal in functionality to Slack or Discord is straight up delusional. One of the biggest problems with IRC is that there is no immediately obvious way to jump into a channel and browse or search the history. Also, because there are so many IRC clients, and so many servers out there, one person's IRC experience can vastly differ from another's. IRC also doesn't have any of the modern amenities like…

> One of the biggest problems with IRC is that there is no immediately obvious way to jump into a channel and browse or search the history.

There are many solutions available to do this. Many channels publish chat logs publicly, which can be downloaded and searched using grep or your tool of choice. And there are web clients that can do this.

> Also, because there are so many IRC clients, and so many servers out there, one person's IRC experience can vastly differ from another's.

That’s rather the point of a protocol, no? IRC isn’t a platform, it’s a standardized way in which various clients and servers can communicate. Much like email, different clients support features useful for different users.

> IRC also doesn't have any of the modern amenities like emoji reactions or reaction gifs, comment threads, code snippets, plug-and-play third party integrations and web hooks, profile pictures, voice/video chat, screen sharing, or any number of a plethora of other features that BOTH Slack and Discord have.

I consider this a feature. I expect many others would. Constant reaction gifs / emojis / etc seem to be a distraction. I don’t believe I’ve seen these used in a way that had a positive impact on productivity, or effectiveness of communication.

> If you want people to use an open source alternative to Slack or Discord, then people need to build that alternative. IRC, unfortunately, is not it (at least not in its current aged state).

matrix.org / riot.im is what you want. The matrix protocol supports all of these features. Riot is an open source web client for it. I use it regularly and would recommend.

Re: Please don't use Slack for FOSS projects (2015)

#67

Acting like IRC is equal in functionality to Slack or Discord is straight up delusional. One of the biggest problems with IRC is that there is no immediately obvious way to jump into a channel and browse or search the history. Also, because there are so many IRC clients, and so many servers out there, one person's IRC experience can vastly differ from another's. IRC also doesn't have any of the modern amenities like…

Emojis, reaction gifs, ugh. https://drewdevault.com/2019/07/01/Absence-of-features-in-IR...

Why'd you change your Hacker News username?

Re: Please don't use Slack for FOSS projects (2015)

#68

Earlier quoted context omitted.

> Also, because there are so many IRC clients, and so many servers out there, one person's IRC experience can vastly differ from another's. How the fuck did people come to think of this as a negative? One of the stupidest things about "modern" IT services is that the public interface is a user interface instead of a machine readable iterface, so you can't build a user interface that fits your needs or preferences, yo…

Instead of re-inventing the wheel building your own interface, why not just spend that time working on the FOSS project in question? FOSS dogma seems to frequently get in the way of FOSS development. If you aren’t pure and blessed, somehow you are less worthy.

GNOME is an example of a free software project that is actively hostile to suggestions, critiques and code to improve it from outside.

Re: Please don't use Slack for FOSS projects (2015)

#69
post #57
post #29

The biggest problem for me in IRC is lack of good mobile clients. You can't get push notifications and if you want to stay persistently online then you need to keep a perpetual battery-draining socket open. You could setup a relay on your server ,but it's cumbersome and too technical for most people.

My wife uses thelounge (self-hosted instance) as a progressive web application on her Android phone. It supports push notifications and file uploads. Before this, she used IRC Cloud, which also has a convenient mobile application with those features. As for myself, I use Weechat-Android (for about 6 years now) and am very happy with that on my Android phone. It uses a websocket with SSL, so I get notifications and it…

IRC cloud is paid with a monthly subscription right?

Are you using weechat as a relay for the Android client or is it a standalone irc client? Cause to receive notifications a websocket will still have to be always connected.

Re: Please don't use Slack for FOSS projects (2015)

#70
> Slack provides an IRC bridge that lets you connect to Slack with an IRC client.

Which doesn't exist anymore: https://news.ycombinator.com/item?id=16539857. As far as I'm aware, there is no way to connect to Slack anymore without their official client, unless you use something that is either their website in an app wrapper or probably violating their ToS.

Post reply on HN