Deprecating Support for IM and Twitter Channels

We’re making changes to the number of channels that can be used to connect to applications running on the Tropo platform.

Specifically, we’ll be deprecating support for the IM and Twitter channel. The ability to add IM and Twitter bots to Tropo apps will be turned off shortly, and will be turning off servers running these features as of January 28.

Over the last several months, it has become apparent that running an IM bot hosting service is something that cannot be done profitably. When we added IM to Tropo several years ago, the popular IM networks had programs for running bots – bypassing limits in contact lists and message volume, for example. This made it feasible to run a large scale IM bot. However, over the last year, these programs have started to disappear. Our contacts at IM providers have left the companies or been reassigned. It’s become clear that this is a business that public IM providers no longer want to be in.

We’ve tried to keep IM support operational despite the fact that not only have we had no support from IM networks, but we have also had to fight the networks actively stopping and shutting down IM bots. Continuing to do this requires a significant amount of resources, and does not bring in enough revenue to justify the battle.

So we’re shutting down the service.

The logical question that many of you will have next is “what can I do instead?” Unfortunately, we’re not aware of any viable IM bot hosting services. Those that we knew of have all gone away. One alternative is to host one yourself. Building a basic XMPP (Jabber) bot isn’t hard. You just need to sign up with an XMPP host, someone like Gmail or Jabber.org will work for low-traffic bots. There are numerous tutorials and frameworks for building XMPP bots in your language of choice. A discussion thread on Quora has some other ideas.

Once you have a XMPP bot up, you can connect it to other IM networks using XMPP Gateways (also known as Transports). These sign on to an IM network for you, and relay messages to and from an XMPP account. There’s not much in the way of public gateways available, so to go this route, you may need to host your XMPP server and your gateways yourself. Spectrum and Kraken are two popular gateways, and Kraken is available as an easy-to-install plugin for Openfire, an open source XMPP server.

If you have concerns or questions about the shutdown or if you have a large scale bot and want to discuss commercial terms for IM bot hosting, please email support@tropo.com.

6 Responses to “Deprecating Support for IM and Twitter Channels”

  1. Scott Faulkner says:

    This is very disappointing news regarding Twitter. Do you really consider Twitter an IM network?

  2. Adam Kalsey says:

    The way Twitter was implemented in Tropo was as an IM network. We were never a full-featured Twitter client. The only feature that we supported for Twitter was responding to public @ messages. We saw Twitter (in this capacity) as nothing more than a message network where all your messages were public.

    Most customers that need serious Twitter support in their application already bypass Tropo and write directly to the Twitter API.

  3. AJ says:

    Does this mean that all IM functionality will be disabled, including jabber? So, essentially, will xyz@tropo.im account stop sending/receiving messages? Can someone clarify this please.

  4. Mark Headd says:

    AJ – yes it does. IM support will be deprecated effective January 28th.

  5. MT says:

    I’m confused – it’s now near the end of February and I still see IM capability being offered in my applications (at the bottom of the application page). Did something happen to delay the turning off of this feature, or did forget to remove the form on the application pages, or what?

  6. Mark Headd says:

    The UI in the Tropo applications listing is in the process of being updated. That portion of the interface will be removed when the UI update is ready.

Leave a Reply

Please note: By submitting a comment you agree to comply with our Comment Policy. We welcome all comments, positive or negative, but do reserve the right to remove all or part of blog comments that do not comply with our policy.

Additionally, the first time you leave a comment on this blog, it will be held for moderation. After that first comment has been approved, future comments will be posted without delay.

Additional comments powered by BackType