Re:Slack Platform Launch
by danmaz74 on Wednesday December 16, 2015 @03:08AM
(#10742958)
One difference is that with AWS you're the paying customer and have leverage. With FB or Slack, you're a non-paying "partner" and your leverage is almost null.
[ Parent
| on HN ]
Re:Slack Platform Launch
by stanleydrew on Wednesday December 16, 2015 @03:26AM
(#10743022)
Good point. Maybe Salesforce is a better example. Or Github. Don't people build tons of integrations on it?
Re:Slack Platform Launch
by asmosoinio on Wednesday December 16, 2015 @03:17AM
(#10742994)
But companies usually pay for Slack? You pretty much have to to get full history.
Re:Slack Platform Launch
by cromwellian on Wednesday December 16, 2015 @03:28AM
(#10743031)
Consumers pay for iOS, but Apple still bans you from selling your app in the store.
The gatekeeper function of the platform means they can shut you off at any time.
If instead, Slack published a protocol so anyone could author a client, then bots would just be normal chat users, for the most part, on par with regular users, and a bot would simply be something you deploy somewhere to sit in your channels, just like IRC bots.
I think Slack is a great app, very good UI, but I'm a little sick of proprietary messaging. We really don't need proprietary centralized messaging networks. Standardize a federated open protocol and let people compete on the clients and let the community agree on extensions to message payloads that clients pay attention to, or ignore.
Re:Slack Platform Launch
by stanleydrew on Wednesday December 16, 2015 @03:38AM
(#10743058)
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).
cool! we should interoperate :) (we being https://matrix.org)
ps. your https://actor.im/platform page 404s
that's exactly what https://matrix.org is trying to do!
Re:Slack Platform Launch
by chinathrow on Wednesday December 16, 2015 @03:52AM
(#10743103)
Same as with Twitter; remember Meerkat and firehose access as examples.