<?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>Tweeterview Blog</title>
	<atom:link href="http://blog.tweeterview.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tweeterview.com</link>
	<description></description>
	<lastBuildDate>Mon, 28 Dec 2009 04:51:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Beta 1.3 released &#8211; we have removed beta codes</title>
		<link>http://blog.tweeterview.com/2009/12/28/beta-1-3-released-we-have-removed-beta-codes/</link>
		<comments>http://blog.tweeterview.com/2009/12/28/beta-1-3-released-we-have-removed-beta-codes/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 04:51:20 +0000</pubDate>
		<dc:creator>Tweeterview</dc:creator>
				<category><![CDATA[Site Updates]]></category>
		<category><![CDATA[beta version 1.3]]></category>

		<guid isPermaLink="false">http://blog.tweeterview.com/?p=47</guid>
		<description><![CDATA[Things have been moving along nicely with our tweeterview roll out and happily after lots of positive feedback and a few kinks ironed out we are pleased to annouce that we have removed the need to have a beta code to access tweeterview.
Version Beta 1.3 still means we are in Beta, but now anyone with [...]]]></description>
			<content:encoded><![CDATA[<p>Things have been moving along nicely with our tweeterview roll out and happily after lots of positive feedback and a few kinks ironed out we are pleased to annouce that we have removed the need to have a beta code to access tweeterview.</p>
<p>Version Beta 1.3 still means we are in Beta, but now anyone with a twitter account can sign up and use tweeterview without having to request a beta code.</p>
<p>We also have rolled out several other minor fixes, including minor changes to the members logged in area, and fixes to the list of previous tweeterviews that users have conducted.</p>
<p>Our next release will hopefully include the ability to control whether your questions and and answers are tweeted out during the tweeterview or just the teasers.</p>
<p>Happy Festive season to everyone!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweeterview.com/2009/12/28/beta-1-3-released-we-have-removed-beta-codes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beta 1.2 now released</title>
		<link>http://blog.tweeterview.com/2009/12/16/beta-1-2-now-released/</link>
		<comments>http://blog.tweeterview.com/2009/12/16/beta-1-2-now-released/#comments</comments>
		<pubDate>Wed, 16 Dec 2009 01:16:28 +0000</pubDate>
		<dc:creator>Tweeterview</dc:creator>
				<category><![CDATA[Site Updates]]></category>
		<category><![CDATA[tweeterview]]></category>
		<category><![CDATA[twinterview]]></category>
		<category><![CDATA[twitterviews]]></category>

		<guid isPermaLink="false">http://blog.tweeterview.com/?p=35</guid>
		<description><![CDATA[Hi tweeterviewers.
Today we released some changes to Tweeterview that are setting up for the Beta code removal.
This release 1.2 has the following changes
In the members logged in area:

A new dashboard when you log in to tweeterview (designed to make it easier to manage your tweeterviews)
Some auto prompting for key information (time zone management especially) for [...]]]></description>
			<content:encoded><![CDATA[<p>Hi tweeterviewers.</p>
<p>Today we released some changes to Tweeterview that are setting up for the Beta code removal.<img class="size-medium wp-image-38 alignright" title="dash1" src="http://tweeterview.com.s3.amazonaws.com/wp-content/uploads/2009/12/dash1-300x120.png" alt="dash1" width="300" height="120" /></p>
<p>This release 1.2 has the following changes</p>
<p><strong>In the members logged in area:</strong></p>
<ul>
<li>A new dashboard when you log in to tweeterview (designed to make it easier to manage your tweeterviews)</li>
<li>Some auto prompting for key information (time zone management especially) for new users</li>
<li>An easily located invite panel on the new dashboard<img class="alignright size-medium wp-image-41" title="dash2" src="http://tweeterview.com.s3.amazonaws.com/wp-content/uploads/2009/12/dash2-300x111.png" alt="dash2" width="300" height="111" /></li>
<li>Renaming the members menu home button to &#8220;My Home&#8221; &#8211; this was causing some confusion. You can use this to get back to the new dashboard at any time</li>
<li>A very obvious &#8216;Create a tweeterview button&#8217; on the dashboard.</li>
<li>New help tools that wills tart showing up throughout the logged in area for new users.</li>
<li>New pop up calendar tool to enter tweeterview dates when creating or editing tweeterviews</li>
<li>Categories have been added to the tweeterview management screen (this makes it easier now to find similar tweeterviews)</li>
</ul>
<p><strong>On the public side:</strong></p>
<ul>
<li>Improved search functionality<img class="alignright size-medium wp-image-43" title="dash3" src="http://tweeterview.com.s3.amazonaws.com/wp-content/uploads/2009/12/dash3-300x174.png" alt="dash3" width="300" height="174" /></li>
<li>Pagination added on most search screens</li>
<li>Categories on the search / find screen, so you can easily find tweeterviews on topics you are interested in</li>
</ul>
<p>Hopefully these will all make the experience better.</p>
<p><strong>Version 1.3 is likely to include the following:</strong></p>
<ul>
<li>No beta code required for anyone</li>
<li>Ability to turn off live tweeting of the questions and answers but still send out the teasers</li>
<li>Integrated translation widget so that you can load up a finished tweeterview in language of your choice.</li>
</ul>
<p>Let us know your thoughts here or via twitter</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweeterview.com/2009/12/16/beta-1-2-now-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New updates due out this week</title>
		<link>http://blog.tweeterview.com/2009/11/30/new-updates-due-out-this-week/</link>
		<comments>http://blog.tweeterview.com/2009/11/30/new-updates-due-out-this-week/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 07:37:45 +0000</pubDate>
		<dc:creator>Tweeterview</dc:creator>
				<category><![CDATA[Site Updates]]></category>
		<category><![CDATA[beta 1.2]]></category>

		<guid isPermaLink="false">http://blog.tweeterview.com/?p=32</guid>
		<description><![CDATA[Later this week we will be rolling out some changes / updates. Beta 1.2.
These include a new dashboard for logged in members, which makes accessing either your tweeterviews, or tweeterviews you have been invited to, much easier to access.
It also includes some default controls that ensure your profile is setup correctly.
Importantly we will be releasing [...]]]></description>
			<content:encoded><![CDATA[<p>Later this week we will be rolling out some changes / updates. Beta 1.2.</p>
<p>These include a new dashboard for logged in members, which makes accessing either your tweeterviews, or tweeterviews you have been invited to, much easier to access.</p>
<p>It also includes some default controls that ensure your profile is setup correctly.</p>
<p>Importantly we will be releasing the categorisation tool. This enables you to allocate a category to the tweeterview you are running. This will make finding related tweeterviews much easier and also help users know what your tweeterviews are about.</p>
<p>Once this version has launched we will add some basic language translation links to the finished tweeterviews and prepare for an exciting new extension of the basic tweeterview (more later).</p>
<p>Oh yeah and so we don&#8217;t forget we are looking to remove the beta invite codes during December if all goes to plan.</p>
<p>Stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweeterview.com/2009/11/30/new-updates-due-out-this-week/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>#Tweeterview being used in a #hashtag for phishers</title>
		<link>http://blog.tweeterview.com/2009/09/30/tweeterview-being-used-in-a-hashtag-for-phishers/</link>
		<comments>http://blog.tweeterview.com/2009/09/30/tweeterview-being-used-in-a-hashtag-for-phishers/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 10:44:13 +0000</pubDate>
		<dc:creator>Tweeterview</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[hashtag]]></category>
		<category><![CDATA[not twitterview]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[tweeterview]]></category>

		<guid isPermaLink="false">http://blog.tweeterview.com/?p=27</guid>
		<description><![CDATA[An important update:
Currently there is a spam bot propagating messages, that are dragging in users to a site named &#8220;Twitterview&#8221; NOTE this is not TWEETERVIEW!
The messages sent by users and fake accounts are this:
I can see who views my Twitter thanks to this new app! http://bit.ly/3hjbmy #TweeterView
NOTE: DO NOT USE THE SITE linked through to. [...]]]></description>
			<content:encoded><![CDATA[<p><strong>An important update:</strong></p>
<p>Currently there is a spam bot propagating messages, that are dragging in users to a site named &#8220;<strong>Twitterview</strong>&#8221; NOTE this is not <strong>TWEETERVIEW</strong>!</p>
<p>The messages sent by users and fake accounts are this:</p>
<blockquote><p><span><span id="msgtxt4493999353">I can see who views my Twitter thanks to this new app! http://bit.ly/3hjbmy #<strong>TweeterView</strong></span></span></p></blockquote>
<p><strong>NOTE:</strong> <strong>DO NOT USE THE SITE linked through to</strong>. the actual URL is: http://askmatthew.net/twitterview/</p>
<p>This site appears to be a phishing site that gets your Twitter details and then can use those details as they see fit.</p>
<blockquote><p>The reason we are posting this message is that due ot the popularity of TWEETERVIEW and the similarity in name they have been using a HASHTAG #tweeterview .</p></blockquote>
<p>We are not associated with this site in anyway and users of Tweeterview can rest comfortable knowing that we use the proper OAUTH authentication and thus do not capture or use your Twitter details at all.</p>
<p>Do not use the twitterview site at http://askmatthew.net/twitterview/ EVER!</p>
<p>Any questions please feel free to contact us via @tweeterview or by using our contact page.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweeterview.com/2009/09/30/tweeterview-being-used-in-a-hashtag-for-phishers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using Tweets to conduct Interviews</title>
		<link>http://blog.tweeterview.com/2009/09/04/using-tweets-to-conduct-interviews/</link>
		<comments>http://blog.tweeterview.com/2009/09/04/using-tweets-to-conduct-interviews/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 06:28:27 +0000</pubDate>
		<dc:creator>Tweeterview</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[interviewing via twitter]]></category>
		<category><![CDATA[tweeterview]]></category>
		<category><![CDATA[twinterview]]></category>
		<category><![CDATA[twitterview]]></category>

		<guid isPermaLink="false">http://blog.tweeterview.com/?p=24</guid>
		<description><![CDATA[If you are new to Tweeterview, and it is pretty new, we put this site together to fill a void.
Many people were doing Twitterviews, Twinterviews, Tweeterviews etc using twitter, but they were incoherent and disjointed.
We also saw many blogs that had full transcripts of interviews conducted via email which just seemed to waste the space [...]]]></description>
			<content:encoded><![CDATA[<p>If you are new to Tweeterview, and it is pretty new, we put this site together to fill a void.</p>
<p>Many people were doing Twitterviews, Twinterviews, Tweeterviews etc using twitter, but they were incoherent and disjointed.</p>
<p>We also saw many blogs that had full transcripts of interviews conducted via email which just seemed to waste the space on the blog, or in main stream press sites where no space was given at all. Tweeterview aims to fill in that space. As well we wanted to stretch the current paradigm of how interviewing is done. The most modern form if it is video interviews, streaming or synchronized using tools like skype. With microblogging growing so fast it seemed crazy that real time interviews were not happening in a &#8216;prettier&#8217; more friendly way.</p>
<p>While we haven&#8217;t released everything we have in mind for it yet, the current beta version are here to learn from, play with and test madly while we perfect the art of tweeterviewing.</p>
<p>This week we released some important upgrades that improved the speed for the people participating in the interview and we have some more tweaks due out shortly.</p>
<p>If you have any feedback or want to know more you are best to tweet to <a href="http://twitter.com/ireckon" target="_blank">@ireckon</a> or <a href="http://twitter.com/tweeterview" target="_blank">@tweeterview</a> and we&#8217;ll get back to you.</p>
<p>If you want to interview us to find out more about what we are doing then heck use tweeterview!!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tweeterview.com/2009/09/04/using-tweets-to-conduct-interviews/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
