Over a million developers have joined DZone.

The Importance of Preserving the Twitter API Field Guide

This stuff may not be the most important now, but it definitely will be in 50 or 100 years. Continue reading to learn all about it.

· Integration Zone

Build APIs from SQL and NoSQL or Salesforce data sources in seconds. Read the Creating REST APIs white paper, brought to you in partnership with CA Technologies.

I'm a fan of the human elements of this technological shift that is going on in our world. We tend to focus on the technology and the dudes who do the technologies (the cyber is huge), but what will really matter in 50 or 100 years will be the more human aspects of how we did all of this. Trust me, it is hard to make this boring ass API sh*t human in any way, so I am always excited when there are people who soften the hard edges of the gears as they grind forward.

One of the moments that has stood out for me in the last decade was the Twitter API Field Guide created by Taylor Singletary during his time as an evangelist at Twitter. This field guide was removed by Twitter (not sure when, as I just noticed today), but the original blog post remained. Thank the Internet gods for the Internet Archive (and Tyler pointing it out) because a copy of his work still lives on for us all to enjoy.

I wanted to make sure a copy of it lives on beyond Twitter, and the Internet Archive, so I copied (cleaned up) and published on GitHub (ha). While this work may seem out of date and irrelevant, it is art and will be something we will look back on fondly in the future. It shouldn't simply be deleted. This is one of the problems with the constant change we have embraced in the tech space; many things we care about will just be deleted and lost forever.

For me, the Twitter Field Guide represents a specific time in the history of the web, and as I write this post, I realize this was a dark time for API optimism in the Twitter API ecosystem, something that was having an effect on the wider API movement. I think this field guide was a very creative human response as we are struggling with not just the technical of the Twitter API, but the business and politics of operating an API platform at this scale. While it was just one iteration in the API documentation, it is like that vintage auto industry poster from the 1930s and provides us with an important snapshot of this period in time, and should be preserved.

I understand that the documentation is out of date, which is probably why it was taken down, but this reflects what is wrong with technology as our master. It demands that we always march forward, with almost no consideration for human things that exist in the cracks. I do not expect tech companies to maintain everything old, but they should allow for archiving and preservation. I have copied and cleaned up a copy of the Twitter API Field Guide from the Internet Archive and operating as a GitHub repository. If you work at Twitter, please don't ask me to take this down. I'm not trying to disrespect the brand or platform, I'm just trying to keep your history alive. Plus, I have copies, and I'll just keep putting it back up.

I have talked about the API purgatory museum before, and if there are any API relics you'd like to see preserved feel free to drop me a line, and I'll see what I can do. This stuff may not be important now, but it will be in 50 or 100 years. 

The Integration Zone is brought to you in partnership with CA Technologies.  Use CA Live API Creator to quickly create complete application backends, with secure APIs and robust application logic, in an easy to use interface.

Topics:
integration ,apis ,twitter

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}