Just found this opensource.com article about Greenpeace becoming an 'open source' organisation. Quite ironic, since a few months ago I met one of their principal IT managers, who openly mocked our efforts to use #foss and #opensource IT in-house. Greenpeace relies 100% on Google's Gsuite. Any comparison with fair trade coffee was met with a "yeah but this is easier, we just don't care about Google's dubious side."


@Gina the author of that piece is part of a co-op with "open" in the name but their daily driver for collaboration is a Slack channel :/ It's not like there aren't free code alternatives, both hosted and self-hostable:

@strypey @Gina I work for a company who's product is free software, but internally we use Slack for communication too. It's very sad, but the reason for using it is that we *don't* want it self hosted. We operate our own infra, and if it ever goes down, it'd be highly inconvenient if our main form of communication would go down with it.

There'd still be better alternatives, I'm sure, though I haven't tried looking around yet.

@tyil @strypey wouldn't outside hosting solve that problem?

(Although a hosted SaaS product might be easier and cheaper in that case)

@Gina @strypey That would move the problem, and increase complexity for me. Suddenly I have to keep track of a number of VPSes that aren't maintained like the rest of them. It's just not worth the added effort and complexity.

@tyil what about just using a SaaSS that uses free code under the hood, instead of ? Something like:
* .im - gratis, owned and hosted by
* - free for personal use, with extended features for paying enterprise users.
* - gratis hosting for free code and open source projects

@strypey @Gina I think a big factor in choosing Slack is that everybody knows it, so nobody needs to be taught to use it. I'd personally like to see alternatives based on free software, but I doubt I'll be able to convince the boss to hop over to an alternative, now that the entire company is using this already.

One benefit I personally see in Slack is that I can use it with my favourite terminal chat client, WeeChat. I know gitter.im should also work in that regard, but Wire and Zulip both don't have integration with WeeChat as far as I know.

We do use GitLab for our code repositories and CI right now, so perhaps Gitter would be a possibility, but I'd have to make a strategy in how to nudge people towards it first, and that will take time.

> One benefit I personally see in Slack is that I can use it with my favourite terminal chat client, WeeChat

I wouldn't count on that lasting. Slack have taken a number of steps to force users to use their Electron monstrosity, including cutting off IRC and XMPP (classic embrace, extend, extinguish):

If Gitter doesn't already support integration, I'm sure they'd accept a PR.

@strypey @Gina I'm not counting on it to last, but I have something that works right now. I believe it uses the Slack HTTP API, so all data they're trying to gather they can probably still gather.

I know very well that you can't trust a proprietary platform to act in the best interest of its users, and that they will always move towards pushing people towards their own harmful ecosystem.
Sign in to participate in the conversation
Mastodon - NZOSS

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!