191–200 of 226 posts
Earlier quoted context omitted.
Yeah it's a shame XMPP turned out to be unable to keep up with the shift from desktop to mobile. Maybe we should take a crack at a more modern alternative?
We are trying to make so at Actor ( https://actor.im ).
ps. your https://actor.im/platform page 404s
Please guys, no. Don't build your startup on top of another platform. Remember Facebook? Remember Twitter? That 80M is a farce by the VCs that actually re-contributes back into Slack, not so much for you.
Earlier quoted context omitted.
But then you would need to handle all the trouble that come from multiple clients. What if somebody makes a CLI client that does not support file transfers? The experience of official client's users would be worse because now they can't be sure that the other side can do the same things they do. If the protocol were to be upgraded then one would have to wait for all of the vendors to support the new features or we wo…
Additional features that can't gracefully degrade would be a selling point for slack. "Your client does not seem to support video calls, we do, purchase an account here". When it comes to file transfers, a simple link to download the file from slack.com is a good degradation example. Once Slack is installed and the norm, you lose some choice. You're prisoner of the way they want chat to be. I'm sure glad Firefox exis…
If Slack falls then, well, we'll pay the price of migration, but seeing as it is a tool for ephemeral conversations I see it as less of a problem as migrating e.g. my e-mail.
Facebook F8 all over again in the sense of startups throwing the success or failure of their company onto a proprietary centralized system that can block or cut them off for any reason. Or rather, another incarnation of IRC chat bots, email listservs, and stuff that's been around forever as commodity autoresponders, only now it's worth millions in investments to write the equivalent of a weekend hack IRC bot because…
Chat and ChatOps aren't going anywhere, and Slack already has a gaggle of nascent competitors, both commercial and OSS.
If you build on Facebook or Twitter and they tell you to pound sand, it's game over. If Slack does the same, you can add support for everyone else - if you haven't already.
You aren't building a "Slack app," you're building a chat app which happens to support the Slack API. Huge difference.
Here's a fresh integration with Slack Button in Ruby, https://github.com/dblock/slack-bot-server serving a "Hello World" bot. Hope it helps someone.
Facebook F8 all over again in the sense of startups throwing the success or failure of their company onto a proprietary centralized system that can block or cut them off for any reason. Or rather, another incarnation of IRC chat bots, email listservs, and stuff that's been around forever as commodity autoresponders, only now it's worth millions in investments to write the equivalent of a weekend hack IRC bot because…
While you are right that it's very similar to IRC etc you are completely missing the fundamental reason Slack et al are popular: user experience, especially for non-technical people. Not everyone grew up on IRC with bouncers, irssi on a remote server, and their own server where they could upload attachments to in a single keystroke. Now it's true that there are new alternatives for non-technical people such as IRCClo…
As the surveillance engine grows, those of us who have gone through the pains of open-sourcing our workflows will be way ahead of everyone else... but I fear we aren't addressing this main issue which is ease of use/adoption for general user cases.
And no, giving me an API does not make it open.
Short story; we need better FOSS UI/UX.
I feel like the world has lost it's mind slightly. When a 2 year old startup launches an $80m fund. I mean I understand they want to be a platform and can see the strength in funding projects that will empower a platform model but still. This is the point at which I think we're really in a boom heading in that bubble direction, and I was never one to fall in to the trap of calling it a bubble before. Love slack, love…
Earlier quoted context omitted.
For me, by far the biggest difference is the notifications. In HipChat, notifications are both buggy and almost completely unconfigurable[0]. If I sent a message to a colleague while they were offline, they would never get notified of it[1]. Slack notifications always work how I expect and are configurable to the degree I desire. Slack also has a nicer UI and better integrations for us, and generally just always work…
Slack is one of my most annoying and least-effective tools because every single message has a pop up that blocks off a corner of my screen. Slack's notifications lack customization which makes them annoying. Either you get the whole package, intrusive desktop pop up and all, or you get no notification. Where's the option to have sounds but no pop ups? Where's the option to lump notifications so you don't get spammed?
Earlier quoted context omitted.
... Did you just make that up? Slack could still have an awesome UX and be open, people would use it out of choice because it has the best UX.
Not OP but my girlfriend and I are long distance and the 6.0.1 update for Android is causing serious strain on our relationship. I keep sending her taco emojis but all she sees are little boxes with x's in them. If Samsung doesn't push this update to Galaxy 6S soon, I don't know how much longer we'll be together...