<?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>kdmurray.blog &#187; cloud</title>
	<atom:link href="http://kdmurray.net/tag/cloud/feed/" rel="self" type="application/rss+xml" />
	<link>http://kdmurray.net</link>
	<description>The crossroads of life and tech</description>
	<lastBuildDate>Sun, 20 May 2012 21:42:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>A Changing Mobile Landscape</title>
		<link>http://kdmurray.net/2012/05/20/a-changing-mobile-landscape/</link>
		<comments>http://kdmurray.net/2012/05/20/a-changing-mobile-landscape/#comments</comments>
		<pubDate>Sun, 20 May 2012 21:42:23 +0000</pubDate>
		<dc:creator>kdmurray</dc:creator>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[Soapbox]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[laptop]]></category>
		<category><![CDATA[mobility]]></category>
		<category><![CDATA[notebook]]></category>
		<category><![CDATA[phones]]></category>
		<category><![CDATA[portability]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[tablets]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://kdmurray.net/?p=1274</guid>
		<description><![CDATA[For the past year or so I&#8217;ve been trying to decide what laptop to buy. My current machine, a 2006 MacBook, is on its last legs and really hasn&#8217;t been an effective mobile computer for over a year due to a drastically shortened battery and what appears to be a busted wifi antenna. The machine [...]]]></description>
			<content:encoded><![CDATA[<p>For the past year or so I&#8217;ve been trying to decide what laptop to buy. My current machine, a 2006 MacBook, is on its last legs and really hasn&#8217;t been an effective mobile computer for over a year due to a drastically shortened battery and what appears to be a busted wifi antenna. The machine has done great things for me for the past several years and is the primary machine from which I&#8217;ve authored most of the posts on this blog. It managed to get me started with podcasting and has been my primary development machine for nearly all my programming projects, regardless of platform. The machine still performs quite well considering its age and how much I&#8217;ve used it over the past five-and-a-half years, really the biggest reasons for me to upgrade it are its newfound lack of mobility (no battery or wifi) and its lack of ability to run OS X Lion and by extension the new version of XCode because Lion will not run on the Core Duo line of processors.</p>

<p>The logical step seemed to be replacing the 13&#8243; MacBook with another MacBook of similar size and capability. The natural contenders were the MacBook Pro and the MacBook Air, both 13&#8243; models. Most of the decision for me had started to revolve around the specs of those machines. Which one could hold more RAM? Which could have a larger hard drive? Do I need an optical drive? These questions plagued me for a number of months and I continued to debate which of these laptops was the right fit for me. One day, while browsing the web looking for indications of an upcoming refresh of the MacBook line I had a bit of an epiphany. I needed to follow the advice at I&#8217;ve given to friends and family for years when it comes to technology &#8212; don&#8217;t focus on the specs, decide what it is that you want or need the technology to do. This was an exercise that I had completely failed to undertake.</p>

<h3>Understanding My Technical Needs</h3>

<p>As I began to examine just what I used technology for on a daily basis some themes began to coalesce from the jumbled mishmash of devices, services and applications. When the patterns first became visible I was a bit surprised, mainly because they were leading me down a path I didn&#8217;t expect &#8212; a path which I had felt until now was for the less geeky, the non-power-user&#8230; <em>the normals</em>. My analysis was telling me that I didn&#8217;t need to get a mid- to high-end laptop, in fact it was starting to look like I didn&#8217;t need a laptop at all&#8230;</p>

<p><strong>How did I come to this conclusion?</strong></p>

<p>In any given week there are a number of things that I use computers for, typically all of these tasks have been done on my main laptop which was the centre of my digital life. When I looked over list list closely, the first pattern began to emerge.</p>

<ul>
<li><a href="http://aussiegeekpodcast.com/">Podcasting</a></li>
<li>Audio Editing</li>
<li>Working with family <a href="http://flickr.com/photos/kmsquared/">photos</a></li>
<li>Software development</li>
<li>Blogging</li>
<li>Writing</li>
<li>Watching video podcasts</li>
<li>Reading blogs and news sites</li>
<li>Casual gaming</li>
</ul>

<h3>Power User Tasks</h3>

<p>Some of these tasks are really best suited to the stationary environment that my MacBook has been confined to for the past many months &#8212; it&#8217;s better to be at a desk with a big screen, a fixed setup and a hard-line to the Internet. The big screen is particularly important for me when I&#8217;m working on software projects, editing audio and working on photos. Having the extra screen real estate for toolbars and being able to get into the details of a photo makes those tasks more enjoyable when I can plug the screen into my laptop. These tasks also require a computer with a reasonable bit of power, but still nothing I would call a powerful workstation.</p>

<h3>Light Content Creation</h3>

<p>By contrast, I prefer to do my blogging and writing when I&#8217;m not confined to my desk. These are tasks I&#8217;ve really enjoyed having the laptop for because they&#8217;ve allowed me to get out and write in other locales, whether its in my living room, in bed or at the local coffee shop. The portability of a mobile device allows me to be wherever my creative juices will flow, and where I can even get some sunshine on occasion. These tasks, however, don&#8217;t require particularly powerful hardware. Even the most basic laptop with a wifi connection is enough to be able to take on most small writing projects and blogging assignments.</p>

<h3>Casual and Mobile Applications</h3>

<p>The last set of tasks fall neatly into the &#8220;content consumption&#8221; category. These are also tasks that I would very rarely do at my desk, but would rather read and watch with other people doing the same kinds of things, such as my wife and I reading for a bit on a Sunday afternoon during our daughter&#8217;s nap. This means that I definitely don&#8217;t want to be tied down to my desk in the basement, mobility is a key feature for these use cases.</p>

<p>Looking through these three groups of tasks, or use cases, a brand new 13&#8243; MacBook Pro would fit the bill quite nicely. It has the power and expansion ports to take care of all of the power-user tasks quite handily. The 13&#8243; size is still small enough to make the device nice and portable so that I can take on all of my writing assignments wherever the mood strikes me, and I could still use it for reading blogs and watching video podcasts.</p>

<p>As I thought about it more I also realized that there were some down sides to my one-machine-to-rule-them-all approach. The first being the cost of mobility. Every time I want to switch between my power-user setup and my mobile setup, I have to detach all of The devices from the MacBook, and then reconnect everything the next time I want to code or podcast. While these could definitely be considered trivial problems to solve, my inherent geek laziness doesn&#8217;t relish the prospect of continually connecting and disconnecting cables for the next four or five years. There is also the issue of heat with the higher-powered MacBook. They do run fairly hot, and whenever I use one for more than 10-15 minutes on a couch or some other similarly loungy position I find the need to place a towel or pillow between me and the device just to keep myself cool (being careful to keep the fan vents clear of course). Lastly was the price, the mid-range MacBook Pro with more RAM and AppleCare would set me back a bit more than $2000 after taxes. While not insurmountable, it&#8217;s certainly not a trivial amount of money.</p>

<h3>The Rethink</h3>

<p>After having considered my options a bit more carefully I began to realize that having a portable desktop-replacement like the MacBook Pro really wasn&#8217;t what I needed. I don&#8217;t write code away from my desk (except on a few very rare occasions), and I certainly don&#8217;t podcast away from my desk. When I looked at my mobile use cases, a great many of them could easily be accomplished with a a much lighter device -<em>gasp</em>- a tablet. In some cases the tablet experience would arguably be better than the computer experience. The tasks I wasn&#8217;t convinced would be good on a tablet were the writing and blogging tasks. My experiences trying to write using the onscreen keyboard of my iPhone had convinced me that I was going to need a physical keyboard to do that kind of work. That said, there are physical bluetooth keyboards available for tablets which can make that experience very similar to working with a laptop. The external keyboard has the added advantage of being removed and stowed when not in use.</p>

<p>Now the catch here (because there&#8217;s always a catch) is that the tablet can&#8217;t handle the more powerful scenarios laid out in my <em>Power User Tasks</em> section above. It&#8217;s limited storage, memory, processing power and screen real estate meant that I would still need another solution to supplement the tablet. This will likely be a mid-range Core i5 or Core i7 Mac Mini, but the need for that device isn&#8217;t quite as urgent, so the existing stationary MacBook will continue to fill that role until the next refresh of the Mini line, hopefully around the same time as the Mountain Lion launch.</p>

<h3>Decision</h3>

<p>With that last piece of the puzzle out of the way, I reached a final decision to extend my Apple ecosystem and picked up a 32GB 3rd generation iPad earlier last week. I have some additional tools coming to supplement the device including a case, a keyboard and a stylus, but details on those will have to wait for another blog post. So far I have been able to do all of my mobile tasks on the iPad, including writing. I banged out this entire post on the iPad using the on-screen keyboard. There were certainly more errors here than on a physical keyboard but it&#8217;s certainly serviceable.</p>

<p>Admittedly I didn&#8217;t give much consideration to purchasing a non-iPad tablet. This is partly because of my existing Apple &#8220;lock-in&#8221; with the iOS devices I&#8217;ve had in The past, including my iPhone, there is some amount of money invested in software. Having all of Those applications instantly available on my new iPad is nice. In addition, the iPad and iOS are a known quantity more than the other tablets.</p>

<p>While it has only been about 5 days since I made the decision to essentially abandon my use of laptops for the next few years (with the exception of my office-issued machine) I&#8217;m really enjoying it so far. There will undoubtedly be more to come on this topic as I learn everything I can about integrating this newest piece of technology into my workflows.</p>
]]></content:encoded>
			<wfw:commentRss>http://kdmurray.net/2012/05/20/a-changing-mobile-landscape/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Security for Client Applications: OAuth</title>
		<link>http://kdmurray.net/2010/11/26/security-for-client-applications-oauth/</link>
		<comments>http://kdmurray.net/2010/11/26/security-for-client-applications-oauth/#comments</comments>
		<pubDate>Fri, 26 Nov 2010 07:42:41 +0000</pubDate>
		<dc:creator>kdmurray</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Soapbox]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[cloud computing]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[services]]></category>

		<guid isPermaLink="false">http://kdmurray.net/?p=850</guid>
		<description><![CDATA[Recently I was listening to Security Now when the topic of OAuth keys being hacked out of Android applications came up. There was some discussion on how services that require OAuth for authentication (as Twitter now does) cause problems for client applications. (NB: In this post I&#8217;m referring to client applications specifically as something that [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://kdmurray.net/wp-content/uploads/2010/11/oauth-logo11.png"><img class="alignleft size-full wp-image-864" title="oauth-logo" src="http://kdmurray.net/wp-content/uploads/2010/11/oauth-logo11.png" alt="" width="200" height="60" /></a>Recently I was listening to <a href="http://twit.tv/sn" target="_blank">Security Now</a> when the topic of <a href="http://oauth.net/about/" target="_blank">OAuth</a> keys <a href="http://www.techeye.net/security/gaping-hole-found-in-twitter-oauth-authentication-process" target="_blank">being hacked out of Android applications</a> came up. There was some discussion on how services that require OAuth for authentication (as Twitter now does) cause problems for client applications. (NB: In this post I&#8217;m referring to client applications specifically as something that the end user downloads to their PC or other device.) The case was made that the problem is that OAuth was not written for client development, and is really only secure when running from a web-server.</p>

<p>The key to the &#8220;vulnerability&#8221; with OAuth is that each application is given its own key. That key ties any request made to the service (Twitter for example) to the application which owns the key. The concern was that if the key falls into the wrong hands users&#8217; personal information could be put at risk. With the key needing to reside somewhere that the application can read it, they&#8217;re typically stored within the application code which makes finding the key a trivial matter for a hacker.</p>

<p>The thought occurred to me that if you need to access a web-based service which requires OAuth, it might be helpful to have an intermediary service handle that authentication for you. By adding a service tier which authenticates a specific user of your application and performs all of the direct interaction with the service there&#8217;s no need to keep the OAuth keys on the client which makes them much more difficult to compromise.</p>
]]></content:encoded>
			<wfw:commentRss>http://kdmurray.net/2010/11/26/security-for-client-applications-oauth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Docs Adds Cloud Storage</title>
		<link>http://kdmurray.net/2010/01/13/google-docs-adds-cloud-storage/</link>
		<comments>http://kdmurray.net/2010/01/13/google-docs-adds-cloud-storage/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 07:38:32 +0000</pubDate>
		<dc:creator>kdmurray</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[docs]]></category>
		<category><![CDATA[files]]></category>
		<category><![CDATA[GDrive]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Docs]]></category>
		<category><![CDATA[sharing]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[types]]></category>

		<guid isPermaLink="false">http://kdmurray.net/?p=819</guid>
		<description><![CDATA[Google Docs today expanded the functionality of the service by offering 1GB of cloud storage for any type of file you want to upload. The only restrictions seem to be the 1GB cap on storage (you can buy more at $0.25 USD / GB) and the limit of 250MB per individual file. Though it doesn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>Google Docs today expanded the functionality of the service by <a href="http://googleblog.blogspot.com/2010/01/upload-your-files-and-access-them.html" target="_blank">offering 1GB of cloud storage</a> for any type of file you want to upload. The only restrictions seem to be the 1GB cap on storage (you can buy more at $0.25 USD / GB) and the limit of 250MB per individual file.</p>

<p>Though it doesn&#8217;t quite match some of the other features we&#8217;ve become accustomed to seeing in cloud storage like an OS client with drag &amp; drop functionality, it certainly provides a reliable place to store some of your larger files that won&#8217;t fit under the smaller 20MB cap that Google places on email. This is quite possibly the precursor to the much lauded and speculated about G-Drive cloud storage service.</p>

<p>via <a href="http://lifehacker.com/5446337/" target="_blank">LifeHacker</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kdmurray.net/2010/01/13/google-docs-adds-cloud-storage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Object Caching 439/450 objects using disk: basic

Served from: kdmurray.net @ 2012-05-23 08:40:27 -->
