Hacker News Reader

Comment by suprasanna | Hacker News Reader

I'm a little confused as to the Twilio reference. Does this mean Chute will allow users to MMS images to a phone number with a server backend?

View on HN

From what I can tell, this would be better called "Zencoder for photos", not "Twilio for photos".

I think they just mean that it's supposed to be an easy, versatile API for photo integration into whatever web app you're working on, like how Twilio is an API for phone integration.

You know that product {X} has arrived when it's assumed to be so mainstream that is's being used to describe functionality {Y} in sentences like "it's like {X} for {Y}".

There used to be a great site: http://nowthatswhaticallstartups.com/ but it appears to be down now unfortunately.

The Twilio reference is more a nod to how effective Twilio has been at making voice accessible to developers.

It's more an analogy and definitely not the ideal, most precise way to describe what we do.

We're much more likely to consider ourselves akin to Heroku as we offer infrastructure and connections to services that make deploying and running super simple. Not to say that Twilio doesn't accomplish the same for tons of folks.

Me too, and I work at Twilio.

Isn't twilio working on allowing web apps to receive MMS messages? I assumed this is what Chute is intending to do.

MMS would be very cool - we support web services, email, mobile and would love to add MMS.

I'm sure we'd use Twilio to accomplish it as well :)

Let's talk, happy to buy you a beer and take a list of feature requests. You know where to find me. :)

Guys, what about multipart SMS message sending/receiving, and 6 sms/minute speed limit?

Reply on news.ycombinator.com