<?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>Mark Stanley &#187; development</title>
	<atom:link href="http://www.ragorder.com/category/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ragorder.com</link>
	<description>ragorder.com</description>
	<lastBuildDate>Fri, 30 Sep 2011 12:46:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Twitter Test Account &#8211; Testing the Twitter API with a temporary account</title>
		<link>http://www.ragorder.com/twitter-test-account-testing-the-twitter-api-with-a-temporary-account/</link>
		<comments>http://www.ragorder.com/twitter-test-account-testing-the-twitter-api-with-a-temporary-account/#comments</comments>
		<pubDate>Tue, 26 May 2009 13:47:25 +0000</pubDate>
		<dc:creator>Mark Stanley</dc:creator>
				<category><![CDATA[api]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[tweet]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[webdev]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[twitter api]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://www.ragorder.com/blog/?p=119</guid>
		<description><![CDATA[I&#8217;ve recently been doing some development work with the Twitter REST API, and I ran into an interesting dilemma &#8211; what to do when I want to test a post &#8211; and especially a batch-post? In my case I don&#8217;t really want to use my live account, as I have an established account with followers [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.ragorder.com%2Ftwitter-test-account-testing-the-twitter-api-with-a-temporary-account%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.ragorder.com%2Ftwitter-test-account-testing-the-twitter-api-with-a-temporary-account%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I&#8217;ve recently been doing some development work with the <a href="http://apiwiki.twitter.com/" rel="nofollow">Twitter REST API</a>, and I ran into an interesting dilemma &#8211; what to do when I want to test a post &#8211; and especially a batch-post? In my case I don&#8217;t really want to use <a href="http://www.twitter.com/markstanley">my live account</a>, as I have an established account with followers I will surely annoy. I really want to do this quietly on a Twitter test account &#8211; so that nobody sees the updates, and nobody knows it&#8217;s me messing around. There&#8217;s no such thing as a developer account if you are a mere mortal like me with a standard un-whitelisted account. The answer is quite simple. You should:</p>
<ol>
<li><a href="https://twitter.com/signup" rel="nofollow">Create a test twitter account</a></li>
<li>Protect your updates</li>
<li>Do your testing and bugfixing</li>
<li>Change the Name, Username, and Email under account settings</li>
<li>Delete the account</li>
<li>Do the real thing on your live account</li>
</ol>
<p>See below for step-by-step instructions on how, and why to do all this.</p>
<p><span style="font-weight: bold;">1. Create a test twitter account</span><br />
First thing you want to do is create a test twitter account so that the junk you upload won&#8217;t pollute your live production account stream, and also won&#8217;t be seen publicly (see point 2.) since if you&#8217;re like me, you&#8217;ll be making many mistakes before you get things working right! Create your test account in the usual way <a href="https://twitter.com/signup?commit=Join%21" rel="nofollow">here</a>.</p>
<p><span style="font-weight: bold;">2. Protect your updates</span><br />
To avoid your updates appearing in the public timeline, search, and other third party apps and twitter sites, as well as to avoid people following you without your permission, it&#8217;s a good idea to &#8216;protect your updates&#8217;. You can do this by clicking Settings, check &#8216;Protect my updates&#8217; and &#8216;hit Save&#8217;.</p>
<p><span style="font-weight: bold;">3. Do your testing and bugfixing</span><br />
You can now play around with the Twitter API. Do your updates, follows, favourites &#8211; all that stuff. Fix your bugs, test again and get to the point where you are happy with your code. Note that if you&#8217;re doing more than just &#8216;updates&#8217; (ie: posts) and more than 100 requests per hour, you&#8217;ll need to get your account or IP whitelisted. You can find out more about this <a href="http://apiwiki.twitter.com/FAQ#IkeephittingtheratelimitHowdoIgetmorerequestsperhour" rel="nofollow">here</a>.</p>
<p><span style="font-weight: bold;">4. Change your account settings</span><br />
Now you are done with your testing and bugfixing, but you&#8217;re a good Twitter citizen and you want to delete your account so someone else can use it &#8211; maybe even you. Since it&#8217;s difficult to re-register the same account name once the account is deleted, and since it&#8217;s impossible to signup under the same email address again, it&#8217;s important that you change these settings before you go ahead and delete your account. Thankfully, this is a simple process. You simply go to Settings, and change the Name, Username, and Email settings to something other than what they are already, enter your password and hit Save. Note: To reduce the chances of using up a useful account name, please consider making the new one as usless as possible &#8211; eg: 986sfsdfkjlblah.</p>
<p><span style="font-weight: bold;">5. Delete your account</span> You&#8217;ve done the right thing, and changed the account details. Now you simply hit &#8216;Delete my account&#8217; at the bottom left of the Settings screen, confirm and you&#8217;re done. Someone else, including you, can now signup for that original account name again. Don&#8217;t you feel good about that ?</p>
<p><span style="font-weight: bold;">6. Now do the real thing</span> Now you can go update your script to reference your real account login, and go do your bad-ass thing on your live account without fearing making any major screw-ups on your precious live Twitter feed.</p>
<p>It would be great if Twitter would introduce the concept of a Developer Account, or test posts that are visible only to the poster in a live account, but in the meantime the above is the best way to go about doing things.</p>
<p>Hope this has proven useful. Please leave a comment below if so.</p>
<p>Be seeing you &#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ragorder.com/twitter-test-account-testing-the-twitter-api-with-a-temporary-account/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

