Hey everyone!
Hoping someone can help us - after the CoTech gathering over the last few days it seemed like the slack channel that lives here > Slack was to be re-ignited
Would love it if the code-operative email domain could be added to the sign up form so we could access it, pretty please <3
Same here, please could our domain be added, thanks
Hey! Finn added Louise and me to it yesterday, he’s an admin if that helps. I’ll post in the slack channel and mention that you need added
amazing thanks Sarah!
Hey that is cool but instead of investing time and energy into Slack which is not a good choice for hopefully obvious reasons, we could also re-orientate ourselves to chat on a co-op run and managed solution?
It’s already up and running. We’ve been building up a group since we posted on Experimental CoTech self-hosted matrix room - it’s not experimental any more, it’s fully functional and anyone can join in.
I did update the allow list of domains for slack to:
agile.coop,blake.house,fairmondo.uk,enspiral.com,gildedsplinters.coop,glowboxdesign.co.uk,gofreerange.com,mediaco-op.net,open-ecommerce.org,outlandish.com,calverts.com,seedsforchange.org.uk,seestep.com,tableflip.io,thesmallaxe.com,wave.coop,weareopen.coop,web.coop,webarchitects.co.uk,calverts.coop,principlesix.coop,secure.coop,thesmallaxe.org,mediablazehosts.coop,creative.coop,code-operative.co.uk
But then deleted that list and replaced it with the one we use for CoTech group membership here:
3xe.co.uk,agile.coop,animorph.coop,blake.house,calverts.coop,commonknowledge.coop,creative.coop,formandfunction.coop,foundersandcoders.com,gildedsplinters.coop,glowboxdesign.co.uk,gofreerange.com,goodpraxis.uk,infactcoop.com,jarrow-insights.co,mc3.coop,mediablazehosts.coop,mediaco-op.net,netuxo.co.uk,open-ecommerce.org,outlandish.com,paperrhino.co.uk,sleuth.coop,uniteddiversity.coop,wave.coop,weareopen.coop,webarchitects.coop,web.coop,opendataservices.coop,aptivate.org,dcdc.io,alpha.coop,secure.coop,tableflip.io,dotproject.coop,goodpraxis.coop,changelab.io,solidarityeconomy.coop,dev.ngo,yvant.coop
However I expect that we need to update this list?
Personally I’d much prefer to use Matrix because it’s our own. I think that we’re building a commons economy, and in cases like this where commons tooling is such a low hanging fruit, I really think we should take it?
Are there any good reasons to use Slack, other than that lots of people know what it is?
The Matrix channel is already reasonably active. I guess the worst-case scenario is having two separate CoTech channels
I think so… our domain doesn’t seem to be in that second list so we still don’t have access 
I’ve added Code Operative’s domain, the full list of domains on the allow list for email signup for the CoTech members group here and for the slack channel
3xe.co.uk,agile.coop,animorph.coop,blake.house,calverts.coop,commonknowledge.coop,creative.coop,formandfunction.coop,foundersandcoders.com,gildedsplinters.coop,glowboxdesign.co.uk,gofreerange.com,goodpraxis.uk,infactcoop.com,jarrow-insights.co,mc3.coop,mediablazehosts.coop,mediaco-op.net,netuxo.co.uk,open-ecommerce.org,outlandish.com,paperrhino.co.uk,sleuth.coop,uniteddiversity.coop,wave.coop,weareopen.coop,webarchitects.coop,web.coop,opendataservices.coop,aptivate.org,dcdc.io,alpha.coop,secure.coop,tableflip.io,dotproject.coop,goodpraxis.coop,changelab.io,solidarityeconomy.coop,dev.ngo,yvant.coop,webarchitects.co.uk,code-operative.co.uk
I agree that having our own open source and self hosted chat platform would be better than using Slack.
We don’t use Slack at Animorph but the session held at the gathering last week indicated that most of the people do use it. There was more interest in coordinating different channels for various needs instead of introducing new services or trying to coerce people into a specific tool.
On the second day of the gathering we started working on mapping needs based on tasks/actions people are looking to engage with. We created a rough diagram @Tucker agreed to improve on and we also made a start on an onboarding tool for people based on their intentions: https://connect.coops.tech/
The Infra page will also benefit from some edits.
Seems like there are ways for people to connect with Slack without having one…
Hopefully the instant messaging channels can converge in some way and become easier to decipher!
It’d be lovely to have everyone using a free-r alternative to slack, but it’d also be lovely to have everyone collaborating and communicating, so I probably wouldn’t let perfect be the enemy of good. I like the idea of bridging the different worlds, so thank you to everyone who works to make that happen. I’d also encourage people to cross-post interesting conversations that are happening here, on slack, or matrix.
@chris - could you add @datacontentreach.co too?
I’m another +1 for Slack as we already use it for ourselves and two clients
We’ve had Slack at WAO for ages and ages, but I think there’s a renewed impetus to experiment with stuff which, as @calummackervoy says, helps build the commons economy. I agree that this shouldn’t be at the expense of getting things done, but Matrix is not difficult.
BTW, I don’t think it’s obvious from this thread, so for those looking for Matrix it’s here: #cooptech:autonomic.zone
(Matrix is decentralised so you’ll either need to self-host or choose a provider such as Element)
I’d love a bridge between element/slack…
Happy for either to be used if there’s a stronger pressence on one or the other…
I mainly wanted access to the slack as most of the CoTech gathering pictures had been posted on there.
Maybe we need another simpling communications session so that the wider network can have their say?
Yea im more than happy to look at the diagram from a design perspective. What’s the best format to create it in? Is it going to sit on the Co-tech site as a flat image or be live text etc?
Slack is proprietary and centralized. That means that people who want to
participate in CoTech would need to enter into an exploitative
relationship with a specific company (that is ofc aiming to use whatever
means to profit).
That also means that people and the collective would be at the mercy of
whatever happens to slack, either the tool or the company. Time and time
again, people and organizations have compromised on “easy and practical”
only to later be forced to move to something else - because the thing
was sold, closed up, their rules changed, started demanding payed plans,
etc.
In my view, compromising on autonomy is a recipe for disaster in the
longer term and also excludes people, right from the start.
To be clear: a bridge to slack would not compromise on autonomy, just on
the security of the communications (as there end to end encryption would
not be possible and slack would have a copy of all). It would require
resources and work also, but it could be an acceptable tradeoff.
Stuff like access to media on slack could be addressed some other way,
though - probably enough to export it and put it up somewhere, with
access for people in those conversations.