Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How about integrating with a protocol instead of adding value to someone else's product?

Have we not learned our lessons from how Twitter treated developers?

Enjoy getting shut off when Slack decide they don't want customers to be adding functionality without paying their per integration rate, or want to stop getting the support tickets from people using your service and confusing it with Slack itself.



Thanks for your feedback. Actually the communication market is picking up. We are not dependant on slack we are an API which can be plugged to any chat service like Hipchat kato etc.


Your company may not be directly dependent on Slack, but if I pay you to use your bot with my Slack system and then Slack pulls the plug, I'm dependent on Slack and your bot working together.

If Slack pulls the plug on your integration and enough of your income is from users who are integrating with Slack, your business could indeed be impacted.


We are working closely with Slack team to get this going. I don't foresee that happening since we promote people to get on board with slack. It's a win win. But I do get your point :) thanks for the feedback.


I'm being facetious, but Twitter clients were a win-win for Twitter too, until they decided they weren't.


True, I totally get that risk :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: