<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>cdevroe.com &#187; json</title>
	<atom:link href="http://cdevroe.com/tag/json/feed/" rel="self" type="application/rss+xml" />
	<link>http://cdevroe.com</link>
	<description>by Colin Devroe</description>
	<lastBuildDate>Thu, 09 Feb 2012 13:49:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<atom:link rel='hub' href='http://cdevroe.com/?pushpress=hub'/>
<cloud domain='cdevroe.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>There&#8217;s a new API in town at Viddler</title>
		<link>http://cdevroe.com/links/viddler-api-v2/</link>
		<comments>http://cdevroe.com/links/viddler-api-v2/#comments</comments>
		<pubDate>Fri, 05 Nov 2010 17:55:03 +0000</pubDate>
		<dc:creator>Colin Devroe</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[bethlehem]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[kyle slattery]]></category>
		<category><![CDATA[pennsylvania]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[viddler]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://cdevroe.com/?p=4348</guid>
		<description><![CDATA[Or, the video in which my head explodes. For more information, see the Viddler developers page. Note: If you are using Google Reader you may not be able to see this video. The Reader team is dragging their feet on supporting Viddler&#8217;s latest embed code. Come on over to my site to see it.]]></description>
			<content:encoded><![CDATA[<p>Or, the video in which my head explodes.</p>
<p><!--[if IE]><object width="640" height="402" id="viddlerOuter-64e54b38" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"><param name="movie" value="http://www.viddler.com/player/64e54b38/"><param name="allowScriptAccess" value="always"><param name="allowNetworking" value="all"><param name="allowFullScreen" value="true"><param name="flashVars" value="f=1&#038;autoplay=f&#038;disablebranding=f"><object id="viddlerInner-64e54b38"><video id="viddlerVideo-64e54b38" src="http://www.viddler.com/file/64e54b38/html5mobile/" type="video/mp4" width="640" height="360" poster="http://www.viddler.com/thumbnail/64e54b38/" controls="controls"></video></object></object><![endif]--> <!--[if !IE]> <!--> <object width="640" height="402" id="viddlerOuter-64e54b38" type="application/x-shockwave-flash" data="http://www.viddler.com/player/64e54b38/"><param name="movie" value="http://www.viddler.com/player/64e54b38/"><param name="allowScriptAccess" value="always"><param name="allowNetworking" value="all"><param name="allowFullScreen" value="true"><param name="flashVars" value="f=1&#038;autoplay=f&#038;disablebranding=f"><object id="viddlerInner-64e54b38"> <video id="viddlerVideo-64e54b38" src="http://www.viddler.com/file/64e54b38/html5mobile/" type="video/mp4" width="640" height="360" poster="http://www.viddler.com/thumbnail/64e54b38/" controls="controls"></video> </object></object> <!--<![endif]--></p>
<p>For more information, see <a  href="http://developers.viddler.com/">the Viddler developers page</a>.</p>
<p>Note: If you are using Google Reader you may not be able to see this video. The Reader team is dragging their feet on supporting Viddler&#8217;s latest embed code. Come on over to my site to see it.</p>
]]></content:encoded>
			<wfw:commentRss>http://cdevroe.com/links/viddler-api-v2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beware: Twitter updated their API a bit</title>
		<link>http://cdevroe.com/notes/twitter-json-update/</link>
		<comments>http://cdevroe.com/notes/twitter-json-update/#comments</comments>
		<pubDate>Thu, 29 Mar 2007 14:32:21 +0000</pubDate>
		<dc:creator>Colin Devroe</dc:creator>
				<category><![CDATA[Notes]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://cdevroe.com/notes/twitter-json-update/</guid>
		<description><![CDATA[Twitter has updated their API and removed a few values from their JSON output but hasn't said anything about it yet, so I thought I would.]]></description>
			<content:encoded><![CDATA[<p>My friend <a href="http://dangerouslyawesome.com/" rel="friend met">Alex Hillman</a> sent me an <abbr title="Instant Message">IM</abbr> yesterday:</p>
<blockquote><p>&#8220;hey, i think twitter might have switched something up on you, on your blog your twitters are there but the time isnt&#8221;</p></blockquote>
<p>After doing a little sniffing around I&#8217;ve found that <a href="http://twitter.com/">Twitter</a> has indeed updated <a href="http://twitter.com/help/api">their JSON output</a> for <a href="http://twitter.com/cdevroe/">my personal timeline</a> on Twitter and removed the &#8216;relative_created_at&#8217; values (which would show things like &#8220;3 hours ago&#8221; on a specific status).  My best guess is that by ripping out this value Twitter is saving themselves an immense amount of calculations on their end.  They still provide you with the date and time that a particular status was stored, so you can still do the math on your end.</p>
<p>I am not sure when they will make this public, or if they are still making subtle changes like this and want to make one update to cover all of the adjustments they are making but I thought I&#8217;d give everyone a heads up that might be using Twitter&#8217;s JSON output(s) to show status on their respective sites or applications.</p>
<p>Update April 5, 2007: Twitter has <a href="http://twitter.com/blog/2007/04/twitter-api-updates-and-new.html">announced API updates</a> as well as written up <a href="http://groups.google.com/group/twitter-development-talk/web/api-documentation">documentation</a> for their API.</p>
<p>[tags]twitter, api, json, update[/tags]<br />
[slug]twitter-json-update[/slug]</p>
]]></content:encoded>
			<wfw:commentRss>http://cdevroe.com/notes/twitter-json-update/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

