121–130 of 176 posts
Earlier quoted context omitted.
$6.67/month is less than $0.33/day (~20 workdays/month)! That's an trivial amount to pay for effective communications in my book.
$0.00/forever is also trivial, with so many OSS alternatives out there.
Also, Matrix.org Open, federated protocol, multiple client and server implementations, integrated IRC bridge.
Earlier quoted context omitted.
> making it poor for community building eh... slack has consistently said that large communities shouldn't use its services. - http://blog.freecodecamp.com/2015/06/so-yeah-we-tried-slack-... Go talk to the hundreds of FOSS communities that use IRC. they have all fixed the persistence / search problem, and there is quite a few high quality mobile and desktop clients for IRC.
> slack has consistently said that large communities shouldn't use its services Apart from the tech problems with 1000+ sized teams, it's insane even considering the free tier with a 10'000 message limitation for 8000+ users.
So the team size isn't itself the problem; instead, it's the idea of wanting 8000 active subscribers in the same single channel that doesn't scale. Doesn't work on Slack; doesn't work on IRC, either.
At the scale of 8000 "viewers", you need the sort of specialized "presentation" software used for managing MOOC lectures and corporate shareholder calls, with fan-out servers, voting indicators, and the ability to "raise your hand" to ask the presiding officer to grant you a temporary +v.
Also, Matrix.org Open, federated protocol, multiple client and server implementations, integrated IRC bridge.
this looks neat, and you can self-host it too.
Earlier quoted context omitted.
Let me know how I can do that just by signing up, because my my job is to work on company problems, not emulate Slack in IRC all day long. No matter how much you push and say that everything Slack offers is doable in IRC, doesn't change the fact that you still have to go through the troubles of setting that stuff up. While I agree that setting up a bot isn't hard, I've done it for the IRC channel I created and still…
Oh please. The tools I use rapidly allow me to chain all sorts of stuff together to create things that surpass even Slack and other apps. Where is a Slack that can do "sensitivity calculation" to alert users of possibly hostile tone? That's right. Not created yet. Give me a half hour and I could have the beginning of that. I also could get translation facilities built in so that English/French/German/Spanish could be…
I wasn't sure when I read the headline if it referred to Slack Linux or Slack the music service. Apparently there is a communications client called Slack, just FYI.
I'm seeing "No e2e encrypted DMs" as one of the cons for most of these.. anyone have a solution?
The only obvious solution, right now, is running your own private server if you want private indexes.
But the One True Way to solve this problem, in the fullness of time, is for every enterprise to run their own little PaaS with a standard API, and for SaaS providers to launch their app instances into the enterprise's PaaS using that API. This would be the cloud equivalent of the SaaS-provider selling the enterprise an "appliance" they can keep within their data-center. The enterprise gets full control of the data: their PaaS can be set up to not allow the SaaS-provider any way to exfiltrate the data the app creates, to determine rollout schedule for new app versions, etc.
(And note that when I say "enterprise", I could just as well mean that any individual user could own their own completely-automated black-box micro-PaaS, living "across" various IaaS providers and migrating to new ones as necessary, brought into existence for them by the first SaaS vendor to try launching something into it. Effectively, the ultimate evolution of a personal VPS, providing you with a "management interface" that looks like a cross between Heroku's dashboard and the Windows "Programs and Features" pane.)
I wish that someone would build an easy-to-use layer on top of an open protocol like IRC or XMPP. The tool could manage setup, configuration, archiving, and notifications. Instead of building a walled garden that is merely accessible via an open protocol, it would be more interesting to build a thin layer on top of an XMPP server that could even be removed or replaced later, if desired.
Earlier quoted context omitted.
If I want to share a diagram with Patrick on our internal Slack --- which we set up in under 10 minutes --- I select the diagram on my desktop and drag it into the window for the Slack channel. Everyone on that channel sees the diagram immediately . I do not give a shit what Slack's buttons look like. I can't do that with IRC. Even if we're all standardized on a modern OSX IRC client, we're still going to end up "sha…
Again, you can use HipChat and get something closer to the best of both worlds; drag-and-drop file sharing with a standard (well… more standard-ish) OS X interface. It's great for you that look-and-feel isn't so important to you, but it is to a lot of people, and that includes myself. At any rate, on Slack, I once drag-and-dropped a text file with the output of a shell script that a colleague wanted to see. He starte…