4 ms·
Not sure why you're getting downvoted. Twitter has a long and sketchy track record with developers. Exhibit A is TwitPic: http://www.digitaltrends.com/social-m
by at-fates-hands 11y ago
Not sure why you're getting downvoted. Twitter has a long and sketchy track record with developers. Exhibit A is TwitPic:
http://www.digitaltrends.com/social-media/twitters-war-on-third-party-developers-continues/ http://www.digitaltrends.com/social-media/twitters-war-on-th...
But what about services that Twitter replicates? The latest applications victimized by Twitter’s in-house team are photo-sharing platforms like TwitPic and YFrog
Back in May, we first heard that Twitter planned to launch its own image posting tool. Up until that point, third party apps were giving Twitter that function. Now that Twitter’s own photo tool has launched, it’s virtually declaring war on the developers who were responsible for creating what has been a very popular aspect of the site.
But you're right, if you take time to develop an app using their API, it might just get their attention and then they'll develop their own version and then cut you completely out.
- joefkelley 11y agoThe crucial difference here is between using a totally open-sourced technology like Storm (or Heron, if they release it) and being a consumer of a public API with a proprietary implementation, or making use of their platform/users/data. Twitter can absolutely block you from their API. Or come out with a competing product that integrates with their own systems better than your product does. But if you're using Storm (or Scalding or whatever), there's really nothing they can do to screw with that.
- saryant 11y agoGP was downvoted for failing to differentiate between relying on Twitter's API and their open source software. The two really can't be compared.