Twitter Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.Anti-spam check. Do not fill this in! === API and developer platform === Twitter was recognized for having one of the most open and powerful developer [[API]]s of any major technology company.<ref>{{Cite news |date=January 11, 2012 |title=Top 10 Web APIs β Bridging Today's Technology |newspaper=WebDAM |url=https://webdam.com/blog/top-10-web-apis_bridging-todays-technology/ |access-date=December 18, 2016}}</ref> The service's API allows other [[web service]]s and applications to integrate with Twitter.<ref>{{cite web |title=Twitter API Wiki / FrontPage |url=http://apiwiki.twitter.com/ |access-date=September 18, 2010 |publisher=Apiwiki.twitter.com}}</ref> Developer interest in Twitter began immediately following its launch, prompting the company to release the first version of its public API in September 2006.<ref>{{cite web |title=Introducing the Twitter API {{!}} Twitter Blogs |url=https://blog.twitter.com/2006/introducing-the-twitter-api |url-status=dead |archive-url=https://web.archive.org/web/20161223145220/https://blog.twitter.com/2006/introducing-the-twitter-api |archive-date=December 23, 2016 |access-date=December 18, 2016 |website=blog.twitter.com}}</ref> The API quickly became iconic as a reference implementation for public [[REST API]]s and is widely cited in programming tutorials.<ref>{{cite web |title=Ruby on Rails Tutorial (Rails 5) |url=https://www.railstutorial.org/book/beginning |access-date=December 18, 2016 |website=Softcover.io}}</ref> From 2006 until 2010, Twitter's developer platform experienced strong growth and a highly favorable reputation. Developers built upon the public API to create the first Twitter mobile phone clients as well as the first URL shortener. Between 2010 and 2012, however, Twitter made a number of decisions that were received unfavorably by the developer community.<ref>{{Cite news |date=March 23, 2016 |title=Twitter's 10 Year Struggle with Developer Relations {{!}} Nordic APIs {{!}} |newspaper=Nordic APIs |url=http://nordicapis.com/twitter-10-year-struggle-with-developer-relations/ |access-date=December 18, 2016}}</ref> In 2010, Twitter mandated that all developers adopt [[OAuth]] authentication with just 9 weeks of notice.<ref>{{cite web |last=Parr |first=Ben |date=April 25, 2010 |title=Twitter Launches Countdown to OAuthcalypse |url=http://mashable.com/2010/04/24/twitter-oauthcalypse/ |access-date=December 18, 2016 |website=Mashable}}</ref> Later that year, Twitter launched its own URL shortener, in direct competition with some of its most well-known third-party developers.<ref>{{Cite news |title=Twitter to launch URL shortener and may block TinyURL and bit.ly |newspaper=ComputerWeekly |url=http://www.computerweekly.com/news/1280092587/Twitter-to-launch-URL-shortener-and-may-block-TinyURL-and-bitly |access-date=December 18, 2016}}</ref> And in 2012, Twitter introduced stricter usage limits for its API, "completely crippling" some developers.<ref>{{cite web |last=Streams |first=Kimber |date=November 11, 2012 |title=Tweetro says it's 'completely crippled' by Twitter's strict 100,000 user token limit |url=https://www.theverge.com/2012/11/11/3631108/tweetro-user-token-limit-api |access-date=December 18, 2016 |website=The Verge}}</ref><ref>{{cite web |last=Wauters |first=Robin |date=August 17, 2012 |title=Twitter API Changes Set Maximum User Cap for 3rd Parties |url=https://thenextweb.com/twitter/2012/08/17/twitter-4 |access-date=May 9, 2013 |publisher=Thenextweb.com}}</ref> While these moves successfully increased the stability and security of the service, they were broadly perceived as hostile to developers, causing them to lose trust in the platform.<ref>{{cite web |last=Ha |first=Anthony |title=Twitter Handcuffs Client Apps With New API Changes |url=https://techcrunch.com/2012/08/16/twitter-api-client-apps/ |access-date=December 18, 2016 |website=TechCrunch|date=August 16, 2012}}</ref> In July 2020, Twitter released version 2.0 of the public API<ref>{{cite web |date=July 16, 2020 |title=Twitter introduces a new, fully rebuilt developer API, launching next week |url=https://techcrunch.com/2020/07/16/twitter-introduces-a-new-fully-rebuilt-developer-api-launching-next-week/ |access-date=April 28, 2022 |website=TechCrunch}}</ref> and began showcasing Twitter apps made by third-party developers on its Twitter Toolbox section in April 2022.<ref>{{cite web |date=April 21, 2022 |title=Twitter wants to win back developer trus |url=https://techcrunch.com/2022/04/21/twitter-to-promote-developers-apps-directly-on-its-platform/ |access-date=April 28, 2022 |website=TechCrunch}}</ref> In January 2023, Twitter ended third-party access to its APIs, forcing all third-party Twitter clients to shut down.<ref>{{cite web |title=RIP Third-Party Twitter Clients |url=https://www.pcmag.com/opinions/rip-third-party-twitter-clients |website=PCMag |access-date=April 5, 2023}}</ref> This was controversial among the developer community, as many third-party apps predated the company's official apps, and the change was not announced beforehand. Twitterrific's Sean Heber confirmed in a blog post that the 16-year-old app has been discontinued. "We are sorry to say that the app's sudden and undignified demise is due to an unannounced and undocumented policy change by an increasingly capricious Twitter β a Twitter that we no longer recognize as trustworthy nor want to work with any longer."<ref>{{cite web |title=Twitterrific: End of an Era |url=https://blog.iconfactory.com/2023/01/twitterrific-end-of-an-era/ |website=Iconfactory: The Breakroom |access-date=April 5, 2023}}</ref> In February 2023, Twitter announced it would be ending free access to Twitter API, and began offering paid tier plans with a more limited access.<ref>{{cite web |title=Twitter is shutting down its free API, here's what's going to break |url=https://www.engadget.com/twitter-shutting-off-free-api-prepare-174340770.html |website=Engadget |date=February 8, 2023 |access-date=April 5, 2023}}</ref> Summary: Please note that all contributions to Christianpedia may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Christianpedia:Copyrights for details). Do not submit copyrighted work without permission! Cancel Editing help (opens in new window) Discuss this page