August 10, 2012
Replicon, leading provider of cloud-based time-tracking applications, allows developers to integrate Replicon features with third party applications via the Replicon API. Whether time needs to be tracked for billable hours, project management, employee schedules, or some additional reason; Replicon provides real-time visibility into time, resource, and project data.
What does a tool maker do when his tool breaks? He builds a new tool to patch the broken one. At least that is what David Beckemeyer (Mr Blog) did when his tweeting garage door opener was threatened by the approaching OAuthpocalypse. This date with destiny for all Twitter programmers is the planned June 30th cutoff of basic authentication. At that point all Twitter apps must communicate with the API through OAuth authentication instead of the much less complicated user name/password form of HTTP Authentication. There are many good reasons for this change, which have been repeated endlessly on the Twitter developer forum, but in practice it is a lot of added complexity, more complexity than David wanted to build into his little, simple garage door device.
Previously set to go away today, using the Twitter API with basic authentication will instead be phased out over the next two weeks. During that time, any application still using the older method should switch to OAuth, which has been the preferred method for some time.