<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
    <title>bradchoate.com</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/" />
    <link rel="self" type="application/atom+xml" href="http://bradchoate.com/atom.xml" />
   <id>tag:bradchoate.com,2014://4</id>
    <link rel="service.post" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4" title="bradchoate.com" />
    <updated>2014-09-12T16:38:01Z</updated>
    <subtitle>The man, the legend.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
 

<entry>
    <title>Official iPhone Order Process</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/09/12/official-iphone-order-process" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2814" title="Official iPhone Order Process" />
    <id>tag:bradchoate.com,2014://4.2814</id>

    <published>2014-09-12T16:38:01Z</published>
    <updated>2014-09-12T16:38:01Z</updated>
    
    <summary>Here are the steps to pre-order a new iPhone. Be sure to follow this procedure exactly as outlined to secure...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/09/12/official-iphone-order-process.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Here are the steps to pre-order a new iPhone. Be sure to follow this procedure exactly as outlined to secure your iPhone.</p>

<ol>
<li>Steel yourself at 11:55 AM Pacific time. The battle is about to begin.</li>
<li>Load store.apple.com at 12:00 AM (Pacific time).</li>
<li>Note &#8220;We&#8217;ll be right back&#8221; page in all written languages.</li>
<li>Refresh page.</li>
<li>Shift in your seat uncomfortably.</li>
<li>Check Twitter.</li>
<li>Refresh page.</li>
<li>Look at your clock.</li>
<li>Refresh page.</li>
<li>Post &#8220;Sigh&#8230; Apple Store is still down :(&#8221; to Twitter to let everyone else know.</li>
<li>Refresh page.</li>
<li>Repeat steps 6-7 until 12:35 AM (Pacific).</li>
<li>Observe the &#8220;We&#8217;ll be right back&#8221; page now gives an error.</li>
<li>Post this new information to Twitter immediately.</li>
<li>Refresh page.</li>
<li>Check the Apple Store app on your phone. Observe the same error.</li>
<li>Force quit the Apple Store app and launch it again (this is how you refresh on mobile).</li>
<li>Note the store loads.</li>
<li>Gasp in amazement. (Softly so you don&#8217;t wake anyone.)</li>
<li>Post this to Twitter.</li>
<li>Cautiously tap to buy an iPhone.</li>
<li>Acknowledge the error message. And repeat until it works.</li>
<li>Enter the information to check your upgrade eligibility.</li>
<li>Submit this information and wait 2 minutes. Acknowledge the error and repeat until it works.</li>
<li>If your carrier says you can&#8217;t upgrade yet, take inventory of items you posses that you can sell to pay for the full iPhone list price.</li>
<li>Select your iPhone size, color and capacity.</li>
<li>Note that the iPhone you selected is unavailable.</li>
<li>Try choosing a different color and/or capacity. Find a combination that is available and add to cart.</li>
<li>Acknowledge the error and retry until you get that sucker in the cart.</li>
<li>Hey, you may just do this. Note that it is now 1:30 AM (Pacific).</li>
<li>Tap the &#8220;Checkout&#8221; button.</li>
<li>Acknowledge the error.</li>
<li>Cry softly and try again.</li>
<li>Confirm your address and billing information are correct and submit the order.</li>
<li>Fix the error in your address and billing information and try again.</li>
<li>Acknowledge the error message.</li>
<li>Re-evaluate your life.</li>
<li>Search Google for reviews of the latest Android phones.</li>
<li>Close browser.</li>
<li>Reopen browser and check the Apple Store. Note it is still down.</li>
<li>Tap to submit your order.</li>
<li>Pray.</li>
<li>That&#8217;s it!</li>
<li>Post your success to Twitter.</li>
<li>Go to bed.</li>
<li>Wake up at 4 AM in a cold sweat. Towel off and go back to sleep.</li>
<li>Wake up at 6 AM and realize you&#8217;re not happy with the color choice you made.</li>
<li>Note that at this point, your preferred iPhone size, color and capacity <em>is</em> available for delivery by launch date.</li>
<li>Go to your email and find the link to manage your order.</li>
<li>View order information and take a deep breath and click to cancel the order.</li>
<li>Acknowledge error.</li>
<li>Keep trying.</li>
<li>Confirm cancelation.</li>
<li>Order a new iPhone.</li>
</ol>
]]>
        

    </content>
</entry>

<entry>
    <title>Year of the burger</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/07/16/year-of-the-burger" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2813" title="Year of the burger" />
    <id>tag:bradchoate.com,2014://4.2813</id>

    <published>2014-07-17T05:22:23Z</published>
    <updated>2014-07-17T05:25:30Z</updated>
    
    <summary>Some more stuff about burgers really? I promise this isn&#8217;t turning into a food blog. [View the story &#8220;Year of...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/07/16/year-of-the-burger.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Some more stuff about burgers really? I promise this isn&#8217;t turning into a food blog.</p>

<div class="storify"><iframe src="//storify.com/bradchoate/year-of-the-burger/embed?header=false&border=false" width="100%" height=750 frameborder=no allowtransparency=true></iframe><script src="//storify.com/bradchoate/year-of-the-burger.js?header=false&border=false"></script><noscript>[<a href="//storify.com/bradchoate/year-of-the-burger" target="_blank">View the story &#8220;Year of the burger&#8221; on Storify</a>]</noscript></div>

<p><em>This is a Storify embed post, so you may need to view it on my site to see it in all it&#8217;s iframe&#8217;d glory.</em></p>
]]>
        

    </content>
</entry>

<entry>
    <title>The perfect burger joint recipe</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/07/02/the-perfect-burger-joint-recipe" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2812" title="The perfect burger joint recipe" />
    <id>tag:bradchoate.com,2014://4.2812</id>

    <published>2014-07-03T03:34:33Z</published>
    <updated>2014-07-03T03:39:00Z</updated>
    
    <summary>Here&#8217;s a simple, three-step recipe for creating the perfect burger joint: Great burgers with bacon Great fries Great shakes Few...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="bacon" />
    
        <category term="burgers" />
    
        <category term="fries" />
    
        <category term="shakes" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/07/02/the-perfect-burger-joint-recipe.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Here&#8217;s a simple, three-step recipe for creating the perfect burger joint:</p>

<ol>
<li>Great burgers <em>with</em> bacon</li>
<li>Great fries</li>
<li>Great shakes</li>
</ol>

<p>Few have followed this recipe, and I don&#8217;t understand why.</p>

<p><a href="http://www.in-n-out.com">In-N-Out</a>? Great burgers, but no bacon. Let me repeat: you cannot get an In-N-Out burger with bacon. If you ask, they will say &#8220;no.&#8221; A burger with 20 patties? Sure. Bacon? GO AWAY. Fries are pretty bad (not that great fresh and worthless after they cool off a bit). Shakes are so-so. I get the feeling their shakes and fries are cheap because their prices are sooo low. They could stand to charge more and improve their offering.</p>

<p><a href="http://www.fiveguys.com">Five Guys</a>? Great burgers and bacon (although a little overcooked, typically). Fries are great and plentiful, but no shakes at all. WHAT. They went to the trouble of adding these fancy soda jukebox machines that let you pick from every soda flavor the Coca-Cola company has ever dreamt of, but there&#8217;s no milkshake button (I looked for like an hour). Also, what is with mixing Helvetica and Tekton together in your signage? Stop that.</p>

<p><a href="http://www.superdupersf.com">Super Duper</a>? Ah, here&#8217;s a contender. A little pricey and boutique-ish (well, it&#8217;s a SF-based place, so I understand), but the burgers are good and the bacon is there. <em>Great</em> shakes. Fries are good but could be better.</p>

<p><a href="http://www.shakeshack.com">Shake Shack</a> is great as I recall on all points. But I have to fly to New York to get one and that&#8217;s out of my price range. PLEASE COME TO CALIFORNIA I BEG OF YOU.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>#geekcut</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/05/25/geekcut" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2811" title="#geekcut" />
    <id>tag:bradchoate.com,2014://4.2811</id>

    <published>2014-05-25T20:38:35Z</published>
    <updated>2014-05-25T20:41:19Z</updated>
    
    <summary>Here&#8217;s another Storify collection of a personal favorite set of tweets. [View the story &#8220;#geekcut&#8221; on Storify] If your reader...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="movies" />
    
        <category term="storify" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/05/25/geekcut.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Here&#8217;s another <a href="//storify.com/bradchoate/geekcut">Storify collection</a> of a personal favorite set of tweets.</p>

<div class="storify"><iframe src="//storify.com/bradchoate/geekcut/embed?header=false&border=false" width="100%" height=750 frameborder=no allowtransparency=true></iframe><script src="//storify.com/bradchoate/geekcut.js?header=false&border=false"></script><noscript>[<a href="//storify.com/bradchoate/geekcut" target="_blank">View the story &#8220;#geekcut&#8221; on Storify</a>]</noscript></div>

<p>If your reader doesn&#8217;t show this content, you&#8217;ll have to view it on my site directly.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Fast lane Internet</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/05/18/fast-lane-internet" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2810" title="Fast lane Internet" />
    <id>tag:bradchoate.com,2014://4.2810</id>

    <published>2014-05-19T04:57:53Z</published>
    <updated>2014-05-19T05:03:16Z</updated>
    
    <summary>So recently, the FCC ruled that it&#8217;d be okie-dokey for the Internet to create tiers of service. What follows is...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="storify" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/05/18/fast-lane-internet.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>So recently, the <a href="http://readwrite.com/2014/05/16/net-neutrality-fcc-proposal-open-internet">FCC ruled</a> that it&#8217;d be okie-dokey for the Internet to create tiers of service. What follows is a bit of fun about this very serious issue, one that may very well change the nature of the Internet. I urge you to educate yourself about the real threat of this decision after you read and favorite each of these:</p>

<div class="storify"><iframe src="//storify.com/bradchoate/fast-lane-internet/embed?border=false" width="100%" height=750 frameborder=no allowtransparency=true></iframe><script src="//storify.com/bradchoate/fast-lane-internet.js?border=false"></script><noscript>[<a href="//storify.com/bradchoate/fast-lane-internet" target="_blank">View the story &#8220;Fast lane Internet&#8221; on Storify</a>]</noscript></div>

<p>(If you&#8217;re viewing this through a news reader, the Storify content may not come through; if not, you&#8217;ll have to visit my site to see it.)</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Personal Hold Music</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2014/01/29/personal-hold-music" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2809" title="Personal Hold Music" />
    <id>tag:bradchoate.com,2014://4.2809</id>

    <published>2014-01-30T01:47:45Z</published>
    <updated>2014-01-30T01:47:45Z</updated>
    
    <summary>Here&#8217;s a small innovation I could use from my smart phone (yes, an iPhone): personal hold music. Cause, who likes...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="iphone" />
    
        <category term="muzak" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2014/01/29/personal-hold-music.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Here&#8217;s a small innovation I could use from my smart phone (yes, an iPhone): personal hold music. Cause, who likes muzak? Here&#8217;s how it would work.</p>

<p>You make a phone call to some customer service center. You navigate their tree of options and end up being put on hold while waiting in line for a person to pick up. They then start playing something <em>hideous</em> while you wait. Personally, I think this is designed to encourage people to hang up, reducing their call volume. But: you have a secret weapon&#8230; you&#8217;re calling with a smart phone equipped with <strong>Personal Hold Music</strong>™®.</p>

<p>So, here&#8217;s what you&#8217;d do: you&#8217;d take the phone from your ear and on the screen, there&#8217;d be a convenient button to play <em>your</em> music. What would this do? Well, once playing your music with an active phone call, your smart phone would pay attention to the line&#8230; since you won&#8217;t be able to hear it (cause you&#8217;re listening to your sweet, rockin&#8217; beats). If the sound from the phone call changes to voice communication (versus music), your music will be paused and what the person on other end said will be replayed. That&#8217;s the tricky part&#8212; making the phone recognize when to switch back to the active call. I suppose it would need to do so even for periodic &#8220;there are <em>n</em> people waiting ahead of you&#8221; prompts, but I could live with that.</p>

<p>This is an idea whose time has come.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>My Thoughts on Coin</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/11/15/my-thoughts-on-coin" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2808" title="My Thoughts on Coin" />
    <id>tag:bradchoate.com,2013://4.2808</id>

    <published>2013-11-16T02:07:24Z</published>
    <updated>2013-11-16T02:08:04Z</updated>
    
    <summary>I crave minimalism. So, Coin interests me, but I don&#8217;t think it&#8217;s for me. Here are some quick thoughts on...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/11/15/my-thoughts-on-coin.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>I crave minimalism. So, <a href="https://onlycoin.com/">Coin</a> interests me, but I don&#8217;t think it&#8217;s for me. Here are some quick thoughts on Coin.</p>

<ul>
<li>If you have more than one credit card, the easiest way to get down to carrying one card is cancel the other ones. I have two active<sup id="fnr1-thoughts-on-coin"><a href="#fn1-thoughts-on-coin">1</a></sup> cards: a debit card from my bank (which is accepted like a Visa card) and an American Express card which has a yearly cash back bonus (and important: I don&#8217;t carry a balance month-to-month, period).</li>
<li>If you use Coin and you find yourself at a place that has to imprint the credit card, you&#8217;re out of luck. Hope you brought some cash.</li>
<li>$100 or even $50 (the pre-launch sale price) seems high for this convenience. Especially if the card has to be replaced every 2 years because it runs on a non-rechargeable battery.</li>
<li>I&#8217;ll still need to carry my driver&#8217;s license; this isn&#8217;t for that.</li>
<li>I&#8217;ll still need to carry my transit card. It has a chip on it, so I don&#8217;t think it can be mimicked by Coin.</li>
<li>I&#8217;ll still need to carry my HID building access security card.</li>
</ul>

<p>So, even if I were to buy one of these &#8212; effectively (at launch sale price) a $25/year (due to the battery lifespan) convenience fee &#8212; I&#8217;d still need a decent wallet to hold everything. I couldn&#8217;t get away with a <a href="http://store.apple.com/us/product/HA757ZM/A/hex-solo-wallet-case-for-iphone-5">slim phone card pocket case</a>, for instance.</p>

<p>No, I think the future looks something more like using Passbook or even NFC&#8230; so, no physical cards. Bluetooth LTE identification for building access. A federal and state-approved method for presenting your identification through with phone. Maybe <strong>then</strong> you could just carry one card; one that serves as a backup in case you lose or damage your phone.</p>

<div class="footnotes">
    <ol>
        <li id="fn1-thoughts-on-coin">
            <p>I also carry a <a href="http://simple.com/">Simple</a> card right now. I&#8217;m looking to switch from Chase, so either the Simple or the Chase debit card will be taken out of rotation depending on whether I switch or not. And I love Simple, but so far they don&#8217;t support a joint account very well.&nbsp;<a href="#fnr1-thoughts-on-coin" title="Jump back to footnote 1 in the text.">&#8617;</a></p>
    </li>
    </ol>
</div>
]]>
        

    </content>
</entry>

<entry>
    <title>What Apple Thinks it Knows About You</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/10/09/what-apple-thinks-it-knows-about-you" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2806" title="What Apple Thinks it Knows About You" />
    <id>tag:bradchoate.com,2013://4.2806</id>

    <published>2013-10-09T07:08:34Z</published>
    <updated>2013-10-09T07:08:34Z</updated>
    
    <summary>This is a response to this. Sure, our smartphones can have a lot of personal information in them and much...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/10/09/what-apple-thinks-it-knows-about-you.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>This is a response to <a href="https://medium.com/adventures-in-consumer-technology/a05db813fe6">this</a>.</p>

<p>Sure, our smartphones can have a lot of personal information in them and much of it is shared with &#8220;the cloud&#8221;. Sometimes that&#8217;s the device manufacturer that is supplying services. Sometimes that&#8217;s a third-party company that makes a social network you want to participate in. Whatever. Let&#8217;s talk about Apple, in particular.</p>

<h2>Your identity</h2>

<p>Apple asks you to sign in or register an Apple ID during the setup process for iPhone, but you have the option to skip this step entirely. Doing so will limit certain features of the phone. But if you want to create an Apple ID, Apple asks that you supply your name, your birthdate, a valid email address, telephone number, zip code, city, state, country and home address. But you can about these things. Apple doesn&#8217;t verify any of this information, save for the email address. And having an email address doesn&#8217;t really identify you&#8212; there&#8217;s no credit card involved in getting a Gmail or Yahoo mail account.</p>

<h2>Your credit card information</h2>

<p>Apple will have your credit card information if you give it to them. There are avenues for buying the phone itself with cash. And if/when you sign up for an Apple ID, you&#8217;re asked for a credit card, but you can decline to fill that in. For app purchases, you can always buy iTunes credit from any number of retailers and redeem them for use in the App Store or the iTunes store.</p>

<h2>Your outdoor location</h2>

<p>The GPS and location services on your phone are activated during the setup of the device. If enabled, location services can report the phone&#8217;s location to Apple. If that bothers you, then don&#8217;t enable location services, or turn it off under the &#8220;Privacy&#8221; section of the Settings app.</p>

<h2>Your indoor location</h2>

<p>Again, location services are an opt-in feature. Micro-location still falls under location services which are easily disabled.</p>

<h2>Your behaviour</h2>

<p>If you make purchases in the App Store or iTunes store, Apple can build a purchase profile about you. But no one is holding a gun to your head to buy these things. If you&#8217;re really worried about Apple relating your love for Phish, then you can load your entire CD-ripped collection onto the device through a computer. It&#8217;s also possible to jail break most iPhones and load software onto it through &#8220;alternative&#8221; sources (not recommended, but there you go).</p>

<h2>Your movement</h2>

<p>This part of the article assumes you&#8217;ve bought an iPhone 5s. Well, the A7 processor does track your spatial movement through an accelerometer but this information is only shared with applications that have been given your permission to use it. If you are wary of those apps, then don&#8217;t grant them permission and simply delete them.</p>

<h2>Your face</h2>

<p>Apple will store photos you take with your phone on iCloud in a personal Photo Stream if you have enabled iCloud and Photo Stream to begin with. Apple cannot, however, force you to take selfies even if you do use iCloud.</p>

<h2>Your fingerprint</h2>

<p>The iPhone 5s does use a sensor under the home button to allow you to unlock your device using fingerprint identification. The process for enabling this is simple, but requires a training process that is user initiated. The iPhone will not scan your fingers without enabling Touch ID.</p>

<h2>What Apple Really Knows About You</h2>

<p>So here&#8217;s what Apple can really know, for absolutely certain. That a device of theirs with a particular serial number was purchased and used with a SIM card with a specific serial number and phone number (this is communicated during the phone activation process). That&#8217;s it.</p>

<p>As for any of these other things: Apple will only have them if you give it to them yourself. Your identity, credit card, location, behavior, movement, face and fingerprint are all safe from Apple. Now, your wireless carrier might know more information about both you and your location (based on cell tower usage), but that would be the case regardless of what phone you&#8217;re using.</p>

<p>In short, there&#8217;s nothing to fear here but fear itself.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>We promise not to screw it up</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/05/21/we-promise-not-to-screw-it-up" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2805" title="We promise not to screw it up" />
    <id>tag:bradchoate.com,2013://4.2805</id>

    <published>2013-05-21T15:09:15Z</published>
    <updated>2013-05-21T15:09:15Z</updated>
    
    <summary>Marissa Mayer made the inaugural post to Yahoo!&#8217;s Tumblr blog, announcing they were acquiring the service for $1.1 billion dollars...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="tumblr" />
    
        <category term="yahoo" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/05/21/we-promise-not-to-screw-it-up.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p><a href="http://yahoo.tumblr.com/post/50902111638/tumblr-yahoo">Marissa Mayer made the inaugural post</a> to Yahoo!&#8217;s Tumblr blog, announcing they were acquiring the service for $1.1 billion dollars (all cash). By modern measures, this seems like a pretty good deal. Remember, they also <a href="http://en.wikipedia.org/wiki/GeoCities#Acquisition_by_Yahoo.21">bought GeoCities for $3.6 billion</a> in 1999 (valued at that amount, it was a stock exchange).</p>

<p>But, what gets me is this bit of her post (and echoed in the official press release). It reads, and I kid you not: &#8220;We promise not to screw it up.&#8221;</p>

<p>That&#8217;s in there because Yahoo! has a poor record of not screwing up things. GeoCities, for one. Flickr was on life support until only recently (I think Instagram and the Facebook buyout of <em>that</em> service for $2 billion had something to do with it). <a href="http://waxy.org/2013/04/the_death_of_upcomingorg/">Upcoming.org</a> was another victim of their embrace, languish and shutdown strategy. The <a href="http://archiveteam.org/">Archive Team</a> folks are still backing up that service. Maybe Archive Team should get a head start on Tumblr. Just in case.</p>

<p>But the worst part about that particular sentence is there&#8217;s no way for them to live up to it. No way. Cause, let&#8217;s face it, &#8220;screw it up&#8221; is a pretty subjective measure. And the folks measuring it have a very fine measuring stick:</p>

<ul>
<li>one advertisement, anywhere on Tumblr&#8230; even a whiff: <strong>they screwed it up.</strong></li>
<li>a Yahoo! logo brandishing the site&#8230; even in the footer: <strong>they screwed it up.</strong></li>
<li>switching authentication from Tumblr login to Yahoo! login: <strong>they screwed it up.</strong></li>
<li>changing terms of service in any way that materially benefits Yahoo! or restricts users: <strong>they screwed it up.</strong></li>
<li>repurposing content without permission on another Yahoo! property: <strong>they screwed it up.</strong></li>
<li>removing user content for newly adopted content policy: <strong>they screwed it up.</strong></li>
<li>one additional promotional email for Tumblr users: <strong>they screwed it up.</strong></li>
<li>adding features that promote other Yahoo! services (even if beneficial): <strong>they screwed it up.</strong></li>
<li>adding any sort of posting/upload limit for free users: <strong>they screwed it up.</strong></li>
<li>introducing any paid level of service while reducing features for free users: <strong>they screwed it up.</strong></li>
<li>changing the period at the end of the &#8220;tumblr.&#8221; logo to an exclamation mark: <strong>they screwed it up.</strong></li>
</ul>

<p>So basically, they can&#8217;t touch it at all without breaking that promise.</p>

<p>Literally, she said &#8220;we promise.&#8221;</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Now on the Apple Store: A Dell XPS with OS X</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/05/16/now-on-the-apple-store-a-dell-xps-with-os-x" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2804" title="Now on the Apple Store: A Dell XPS with OS X" />
    <id>tag:bradchoate.com,2013://4.2804</id>

    <published>2013-05-16T16:35:53Z</published>
    <updated>2013-05-16T16:35:53Z</updated>
    
    <summary>Can you imagine an Apple exec, taking the stage at a main Apple event, promoting a Dell computer that has...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="google" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/05/16/now-on-the-apple-store-a-dell-xps-with-os-x.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Can you <em>imagine</em> an Apple exec, taking the stage at a main Apple event, promoting a Dell computer that has been optimized for running OS X, and sold exclusively through Apple&#8217;s own store? Well, that&#8217;s basically <a href="http://bits.blogs.nytimes.com/2013/05/15/google-to-sell-its-own-version-of-samsungs-galaxy-s4/">what Google did</a> yesterday at Google I/O by announcing they were to sell an unlocked, no-contract Samsung Galaxy S4 running the stock Android OS and sold through Google&#8217;s Play store, for $649.</p>

<p>Why did Google buy Motorola for <strong><em>$12.5 billion</em></strong>? And what a slap in the face to all the other Android hardware companies.</p>

<p>The Android ecosystem is truly amazing. And mind boggling.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Google Island</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/05/15/google-island" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2803" title="Google Island" />
    <id>tag:bradchoate.com,2013://4.2803</id>

    <published>2013-05-16T06:33:34Z</published>
    <updated>2014-05-20T01:57:46Z</updated>
    
    <summary>Here&#8217;s a Storify post assembled from a bunch of Tweets I just made inspired by the Google I/O presenation this...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="google" />
    
        <category term="storify" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/05/15/google-island.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Here&#8217;s a Storify post assembled from a bunch of Tweets I just made inspired by the Google I/O presenation this year. Larry Page said there should be a part of the world set aside for unregulated research and science. Well, I think it should be called Google Island&#8230;</p>

<div class="storify"><iframe src="//storify.com/bradchoate/google-island/embed?border=false" width="100%" height=750 frameborder=no allowtransparency=true></iframe><script src="//storify.com/bradchoate/google-island.js?border=false"></script><noscript>[<a href="//storify.com/bradchoate/google-island" target="_blank">View the story &#8220;Google Island&#8221; on Storify</a>]</noscript></div>

<p>(if you&#8217;re viewing this through a news reader, the Storify content may not come through; if not, you&#8217;ll have to visit my site to see it)</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Phishing with Forged Links</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/05/09/phishing-with-forged-links" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2802" title="Phishing with Forged Links" />
    <id>tag:bradchoate.com,2013://4.2802</id>

    <published>2013-05-09T15:17:07Z</published>
    <updated>2013-05-09T15:40:24Z</updated>
    
    <summary>TL;DR version: Sophisticated phishing attacks can be hard to detect for most. As software developers, we need to build better...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="forgedlinks" />
    
        <category term="phishing" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/05/09/phishing-with-forged-links.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p><strong><em><span title="Too Long; Didn't Read">TL;DR</span> version:</em></strong> Sophisticated phishing attacks can be hard to detect for most. As software developers, we need to build better detection, prevention, and countermeasures into apps and services that relay and present these messages so users will be less likely to fall victim to them.</p>

<p><a href="http://theonion.com/">The Onion</a> is a satirical news web site that looks like a legitimate news company. They make their living at spoofing the real news. So, they should be keenly aware of the fact that things aren&#8217;t always as they seem.</p>

<p>Well, recently, their Twitter account was hacked. Compromised by the &#8220;Syrian Electronic Army&#8221;. And now you can read about how they did it. The Onion&#8217;s tech team published an article about it: <a href="http://theonion.github.io/blog/2013/05/08/how-the-syrian-electronic-army-hacked-the-onion/">How the Syrian Electronic Army Hacked The Onion</a>. Go read that now to get some context for what follows.</p>

<p>In short, it was a targeted attack. An email that was baiting the writers at The Onion to come and see an article about their organization. And look&#8212; it&#8217;s on The Washington Post! How exciting. The text of the link was an address that pointed to &#8220;http://washingtonpost.com/&#8230;&#8221;, but the link itself pointed to another site entirely. I&#8217;ve come to call that kind of link a &#8220;forged link&#8221;; a fraudulent and deceptive hyperlink. The phrase also works in the sense that such a link is deliberately <em>crafted</em> to deceive.</p>

<h3>How Forged Links Work</h3>

<p>Stepping back a bit, for those that don&#8217;t understand how that works. An email message can be like a web page, where most anything in the email can be linked to a web site. Could be text, could be an image, or even white space. So, an address to something, like my own web site would be like this:</p>

<pre><code>http://bradchoate.com/
</code></pre>

<p>But see how it isn&#8217;t linked? It looks like an address, and it is, but unless it&#8217;s written <em>this</em> way, it won&#8217;t be usable:</p>

<pre><code>&lt;a href="http://bradchoate.com/"&gt;http://bradchoate.com/&lt;/a&gt;
</code></pre>

<p>This is the HTML representation of a link, and this is how they&#8217;re written, but the bits in-between the &lt; and &gt; symbols are hidden from view when reading a web site or email message, since those are instructions to the computer; not really something for a human to read. But that was me being <strong><em>honest</em></strong>. What if I wrote <em>this</em> instead?</p>

<pre><code>&lt;a href="http://reallybadwebsite.com/"&gt;http://bradchoate.com/&lt;/a&gt;
</code></pre>

<p>and remember, you don&#8217;t get to see it that way in the actual email message. You&#8217;d see it like this:</p>

<p class="pre"><tt><a href="http://reallybadwebsite.com/">http://bradchoate.com/</a></tt></p>

<p>Now then&#8212; the link to my site is still shown, and now it&#8217;s underlined, which means you can click on it. But, where you go when you click on it is somewhere altogether different. That&#8217;s how the forged link works. The link that the unsuspecting recipient at The Onion clicked on did not take them to &#8220;washingtonpost.com&#8221;, but instead, to a different web site that looked very much like a Google.com account login page. When that happened, it should have sent off alarms in the mind of the user&#8212; &#8220;why did that happen?&#8221;. But instead&#8230; at least for one or two that got this far&#8230; they entered their Google credentials and unknowingly sent them to their attacker. And, after sending the login information, they were simply passed over to their actual Gmail account, which probably displayed their email since they were likely still logged into Google.</p>

<h3>Okay, Blame the User, Right?</h3>

<p>The tech guys at The Onion give some advice on how to protect yourself from this kind of attack. But these recommendations put all the onus on the end-users:</p>

<ul>
<li>&#8220;Make sure your users are educated&#8230;&#8221; Right off the bat&#8212; &#8220;the user was wrong, so teach them not to do that!&#8221;. Well, good luck with teaching <em>everybody</em>.</li>
<li>&#8220;The email addresses for your Twitter accounts should be on a system that is isolated&#8230;&#8221; Okay, so if we can&#8217;t avoid these attacks, might as well put their target a little further out of reach.</li>
<li>&#8220;All Twitter activity should go through an app of some kind&#8230;&#8221; Sure, cause nobody would ever attempt to obtain your HootSuite credentials.</li>
<li>&#8220;If possible, have a way to reach out to all of your users outside of their organizational email.&#8221; Not really anything preventative here, just disaster recovery planning.</li>
</ul>

<p>Well, I prefer to place more blame on everyone else.</p>

<h3>Antispam/Antiphishing Filters Failed</h3>

<p>The fact that this email included a forged link like this and was not flagged in some way is frustrating. Computers are great at spotting a discrepancy like this&#8212; especially for pure-text links&#8212; and they should be helping us to be safe.</p>

<p>Of course, it could have been an <em>image</em> of a link to washingtonpost.com that was linked the bad web site. In that case, it may be necessary to use text recognition on images that are linked to see if they&#8217;re misdirecting.</p>

<h3>The User&#8217;s Email Client (Gmail, Apple Mail, Outlook, etc.) Failed</h3>

<p>If the message did reach the inbox, it should be flagged in a way to identify the forged link, and the fact that this is coming from a stranger (someone that has no correspondence history) and as such, links clicked on should be programatically and visually verified.</p>

<p>A programmatic verification would check the domain of the link against a database of known risky web sites. </p>

<p>A visual verification would involve (at a minimum) showing the user the actual link they&#8217;re about to visit. But it could also display a screenshot of the web page so they can see where they are about to go in a safe way before they actually visit the site.</p>

<p><strong>Currently</strong>, some email apps offer some visual verification in the sense that if you put your mouse pointer on top of a link and hold there for a second or two, it will reveal the link address in a &#8220;tip&#8221; window. That&#8217;s <em>cute</em>, but not good enough.</p>

<h3>The User&#8217;s Web Browser Failed</h3>

<p>The user&#8217;s web browser allowed them to enter sensitive information (data into a password field) on a site they&#8217;ve never done that on before. The user should be warned&#8212; even before the keypress registers in the password field&#8212; that they are about to do something potentially risky. <a href="http://www.ismytwitterpasswordsecure.com">Something akin to this</a>, but generalized for any untrusted web site asking for a login (and doesn&#8217;t call you an <em>idiot</em>, ideally).</p>

<p>And again, the web browser could check the domain against a database of risky sites (including all of these free web hosting services, God bless &#8216;em). A stronger warning should be given if the user is trying to enter sensitive information on a web site without a secure connection. These types of attacks rarely ever use a secure web site, since that requires money and creates a paper trail that can be followed.</p>

<h3>We Can Do Better Than This</h3>

<p>To sum up, there are many gaps to be filled in here. As software developers, we have to stop telling people that they are to blame for falling for these tricks. Let&#8217;s at least give them some better tools to arm themselves against the &#8220;Syrian Electronic Army&#8221; and other hackers out there.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Re: unauthorized access</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/05/03/re-unauthorized-access" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2801" title="Re: unauthorized access" />
    <id>tag:bradchoate.com,2013://4.2801</id>

    <published>2013-05-03T15:39:52Z</published>
    <updated>2013-05-06T19:39:14Z</updated>
    
    <summary>Earlier this week, I got the following email from my Mom: From: Mom To: Brad Choate Subject: Fwd: unauthorized access...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="phishing" />
    
        <category term="spam" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/05/03/re-unauthorized-access.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>Earlier this week, I got the following email from my Mom:</p>

<p class="pre"><tt>From: Mom<br>
To: Brad Choate<br>
Subject: Fwd: unauthorized access<br>
<br>
I think you will tell me to ignore this. Right?<br>
<br>
<br>
&#8212;&#8212;&#8212;&#8212;&#8212; Forwarded message &#8212;&#8212;&#8212;&#8212;&#8212;<br>
From: Strife, C Frederic (FRED STRIFE MD) &lt;Frederic.Strife@cchmc.org&gt;<br>
Date: Thu, May 2, 2013 at 4:31 AM<br>
Subject: unauthorized access<br>
<br>
Dear Valued Staff,<br>
<br>
We suspect an unauthorized access on your account. To ensure that your account was not compromised, please click HERE &nbsp; &nbsp; http://updates.a.nf/ &nbsp; &nbsp; to confirm your identity and update your account.<br>
<br>
(c) 2013 Webmaster Inc
</tt></p>

<p>Now, my Mom is not new to computers. She&#8217;s been using them since the &#8217;80s. But she is susceptible to social engineering, because prior to the Internet, she wasn&#8217;t trying to be conned all the time. So, every now and then, she forwards an email like this to me, asking if it is legitimate or not. I typically just give a short &#8220;Nope; just delete that.&#8221; kind of reply, but this time, I decided to give her more to learn from. Here&#8217;s my reply:</p>

<p class="pre"><tt>To: Mom<br>
From: Brad Choate<br>
Subject: Re: unauthorized access<br>
<br>
Yes, you can ignore an email like this. There are too many warning signs to even consider this is valid at all:<br>
</tt></p>

<ul class="pre"><li><tt>Who is &#8220;Frederic C Strife&#8221; and why is he emailing me about my account?</tt></li>
<li><tt>What is &#8220;Webmaster Inc.&#8221; (from the message)?</tt></li>
<li><tt>Why does this Frederic person think I&#8217;m part of his staff (from the message)?</tt></li>
<li><tt>What account is this in reference to in the first place?</tt></li>
<li><tt>What is the &#8220;cchmc.org&#8221; domain (from their email address)? You&#8217;ve probably not seen that address before.</tt></li>
<li><tt>What is the &#8220;updates.a.nf&#8221; domain (from the link they want you to use)? &#8220;nf&#8221; is the domain for Norfolk Island, which is a small island near Australia. What would that have to do with any of my accounts?</tt></li>
<li><tt>Why is this email so short on information if it involves something so serious as unauthorized access to my account?</tt></li></ul>

<p class="pre"><tt>The email subject alone is enough to give me pause: &#8220;unauthorized access&#8221; &#8212; all lowercase, and a phrase that is purely meant to scare you and lure you into this trap.<br>
<br>
At best, it was sent to you by mistake. At worst, it&#8217;s a link that will take you to a web site where it will attempt to install software on your computer than could contain a virus. But in this case, it is sending you to a web page that looks like this:<br>
<br>
<img align="center" src="http://bradchoate.com/images/webmail-phish-attempt.jpg" alt="Webmail Phish Attempt"><br>
<br>
There&#8217;s nothing here that tells you you&#8217;re on a Google property. It isn&#8217;t explaining the situation further at all. It&#8217;s simply asking you to hand over your email address and password. They will then take it and attempt to use it to access your email. Why? To sift through it to obtain information about you, or useful things like information about other accounts. They could also change your password to lock you out of it. An email address is often used as a way to verify access to other accounts. They could request a new password for a bank account or your Amazon.com account (which could be discovered from your email history), which would send information to your (now compromised) email address for how to reset that password.<br>
<br>
So, thanks for asking, but this is just a poor attempt to gain your email account credentials, pure and simple. Don&#8217;t fall for these.<br>
<br>
More information on how to spot these right away:<br>
<br>
<a href="http://www.microsoft.com/security/online-privacy/phishing-symptoms.aspx">http://www.microsoft.com/security/online-privacy/phishing-symptoms.aspx</a><br>
<a href="http://idtheft.about.com/od/preventionpractices/ss/phishing_scams.htm">http://idtheft.about.com/od/preventionpractices/ss/phishing_scams.htm</a><br>
<br>
-Brad<br></tt></p>

<p>This spammer was pretty lazy, actually. This is one of the more obvious ones. Some will mimic an email notification from a legitimate service like Gmail, or Yahoo! Mail. And the website itself is also pretty basic and not an attempt to appear to be any website you might recognize. Even the link in the email is unobscured. My guess is that they don&#8217;t really have to try. There are enough people that will simply click on that link and fill in a form like that without thinking much about it. (I did find it funny that they&#8217;re putting a captcha here&#8230; is this form being spammed?)</p>

<p>Be on your guard. As I explained to my Mom, obtaining your email account can open you up to other problems, including accessing other accounts that may be tied to your email address. At the very least, your email account could be used to propagate more spam and phishing attacks like this one.</p>

<p>Additional resources to educate yourself about phishing:</p>

<ul>
<li><a href="http://www.onguardonline.gov/phishing">OnGuardOnline.gov - Phishing</a></li>
</ul>
]]>
        

    </content>
</entry>

<entry>
    <title>My work tools, 2013 edition</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/04/29/my-work-tools-2013-edition" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2800" title="My work tools, 2013 edition" />
    <id>tag:bradchoate.com,2013://4.2800</id>

    <published>2013-04-29T17:50:01Z</published>
    <updated>2013-04-29T17:50:01Z</updated>
    
    <summary>From year to year my work tools change. So, periodically I like to capture the state of my work environment...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="iusethis" />
    
        <category term="software" />
    
        <category term="work" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/04/29/my-work-tools-2013-edition.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>From year to year my work tools change. So, periodically I like to capture the state of my work environment on my computer. I&#8217;m a software developer (both web and iOS) who dabbles in design. Here&#8217;s the latest snapshot:</p>

<ul>
<li>Computer: 11&#8221; <a href="http://www.apple.com/macbookair/">MacBook Air</a> (Mid 2011) ($$$). My employer has provided me with this laptop, and it&#8217;s the best I&#8217;ve had. Can easily power the 27&#8221; Apple Cinema display I use with it every day and runs everything I need, from Photoshop to Xcode, even with the bevy of OS X menubar items I keep running. 4 GB goes a long way on this Mac. It travels in a <a href="http://www.tombihn.com/laptop_bags/TB0221.html">Tom Bihn Ristretto</a> ($$$) which holds my laptop and a 10&#8221; iPad easily.</li>
<li>Developer Tools:
<strong><a href="https://github.com/textmate/textmate">TextMate 2</a></strong> ($0),
<strong><a href="https://itunes.apple.com/us/app/xcode/id497799835?mt=12">Xcode</a></strong> ($0),
<strong><a href="https://itunes.apple.com/us/app/coderunner/id433335799?mt=12">CodeRunner</a></strong> ($),
<strong><a href="https://itunes.apple.com/us/app/echo/id570935321?mt=12">Echo</a></strong> ($),
<strong><a href="http://www.kaleidoscopeapp.com">Kaleidoscope</a></strong> ($$$),
<strong><a href="https://itunes.apple.com/us/app/dash-docs-snippets/id458034879?mt=12">Dash</a></strong> ($),
<strong><a href="http://www.charlesproxy.com">Charles</a></strong> ($$$),
<a href="http://www.iterm2.com">iTerm 2</a> ($0),
<a href="https://itunes.apple.com/us/app/coderunner/id433335799?mt=12">Patterns</a> ($),
<a href="https://itunes.apple.com/us/app/codebox/id412536790?mt=12">CodeBox</a> ($),
<a href="http://clickontyler.com/virtualhostx/">VirtualHostX</a> ($$$),
<a href="https://itunes.apple.com/us/app/livereload/id482898991?mt=12">LiveReload</a> ($)</li>
<li>Design tools:
<strong><a href="http://www.adobe.com/products/photoshop.html">Photoshop</a> ($$$) (but also own and recommend <a href="https://itunes.apple.com/us/app/pixelmator/id407963104?mt=12">Pixelmator</a> ($$$) and <a href="https://itunes.apple.com/us/app/acorn-image-editor-for-humans/id402280036?mt=12">Acorn</a> ($$$))</strong>,
<a href="https://itunes.apple.com/us/app/coda-2/id499340368?mt=12">Coda 2</a> ($$$),
<a href="http://macrabbit.com/espresso/">Espresso</a> ($$$),
<a href="https://itunes.apple.com/us/app/webcode/id570644822?mt=12">WebCode</a> ($$$),
<a href="https://itunes.apple.com/us/app/xscope/id447661441?mt=12">xScope</a> ($$$),
<a href="https://itunes.apple.com/us/app/paintcode/id507897570?mt=12">PaintCode</a> ($$$),
<a href="https://itunes.apple.com/us/app/hype/id436931759?mt=12">Hype</a> ($$$),
<a href="https://itunes.apple.com/us/app/sketch/id402476602?mt=12">Sketch</a> ($$$),
<a href="https://itunes.apple.com/us/app/omnigraffle/id404458553?mt=12">OmniGraffle</a> ($$$)</li>
<li>Extensions and Menubar items:
<a href="http://createlivelove.com/79/menuanddockless-20/">MenuAndDockless</a> ($0; requires SIMBL, but worth it),
<a href="https://itunes.apple.com/us/app/moom/id419330170?mt=12">Moom</a> ($),
<a href="http://www.macbartender.com">Bartender</a> ($$),
<a href="http://www.pandabarapp.com/">PandaBar</a> ($; unavailable at the moment),
<a href="https://itunes.apple.com/us/app/cloudclip-manager/id563362017?mt=12">CloudClip</a> ($0),
<a href="http://oomphalot.com/sidekick/">Sidekick</a> ($$$),
<a href="https://itunes.apple.com/us/app/popclip/id445189367?mt=12">PopClip</a> ($),
<a href="https://itunes.apple.com/us/app/live-wallpaper/id531123879?mt=12">Live Wallpaper</a> ($),
<a href="https://itunes.apple.com/us/app/fantastical/id435003921?mt=12">Fantastical</a> ($$),
<a href="http://bjango.com/mac/istatmenus/">iStat Menus</a> ($$),
<a href="https://itunes.apple.com/us/app/air-display/id419449718?mt=12">Air Display</a> ($$),
<a href="http://www.apparentsoft.com/trickster/">Trickster</a> ($),
<a href="http://hyperdock.bahoom.com">HyperDock</a> ($)</li>
<li>Utilities:
<strong><a href="http://www.alfredapp.com">Alfred 2</a></strong> ($0; $$$ for the PowerPack),
<strong><a href="https://itunes.apple.com/us/app/1password-password-manager/id443987910?mt=12">1Password</a></strong> ($$$),
<strong><a href="http://db.tt/0OX1D1K">Dropbox</a></strong> ($0),
<strong><a href="https://itunes.apple.com/us/app/textual/id403012667?mt=12">Textual</a></strong> ($),
<a href="http://panic.com/transmit/">Transmit</a> ($$$),
<a href="https://www.crashplan.com/">CrashPlan</a> ($0 for peer-to-peer sync),
<a href="http://www.noodlesoft.com/hazel.php">Hazel</a> ($$$),
<a href="https://itunes.apple.com/us/app/clarify/id455888980?mt=12">Clarify</a> ($$$),
<a href="https://itunes.apple.com/us/app/soulver/id413965349?mt=12">Soulver</a> ($$)</li>
<li>Office Apps:
<a href="http://docs.google.com/">Google Docs</a> ($0),
<a href="https://itunes.apple.com/us/app/pages/id409201541?mt=12">Pages</a> ($$),
<a href="https://itunes.apple.com/us/app/numbers/id409203825?mt=12">Numbers</a> ($$),
<a href="https://itunes.apple.com/us/app/keynote/id409183694?mt=12">Keynote</a> ($$)</li>
<li>Writing Tools:
<strong><a href="https://itunes.apple.com/us/app/evernote/id406056744?mt=12">Evernote</a></strong> ($0),
<a href="https://itunes.apple.com/us/app/ia-writer/id439623248?mt=12">iA Writer</a> ($),
<a href="https://itunes.apple.com/us/app/foldingtext/id540003654?mt=12">FoldingText</a> ($$$)</li>
</ul>

<p>Bold items are essential apps. The others make life easier, but I could get by without them. Price legend (based on today&#8217;s prices; subject to change): $0 = free; $ = less than $10; $$ = more than $9.99, less than $20; $$$ = more than $19.99. I have more apps actually, but I can&#8217;t recommend them as strongly. I have given 5-star ratings to all of the above apps on the Mac App Store.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Catching up</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2013/04/26/catching-up" />
    <link rel="service.edit" type="application/atom+xml" href="http://bradchoate.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=2799" title="Catching up" />
    <id>tag:bradchoate.com,2013://4.2799</id>

    <published>2013-04-26T20:24:00Z</published>
    <updated>2013-04-29T18:26:48Z</updated>
    
    <summary>So I should probably give a bit of a recap to bridge the gap I&#8217;ve created from not posting here...</summary>
    <author>
        <name>Brad</name>
        <uri>http://bradchoate.com/</uri>
    </author>
    
    
        <category term="life" />
    
        <category term="work" />
    
    <wfw:commentRss>http://bradchoate.com/weblog/2013/04/26/catching-up.xml</wfw:commentRss>
    <content type="html" xml:lang="en" xml:base="http://bradchoate.com/">
        <![CDATA[<p>So I should probably give a bit of a recap to bridge the gap I&#8217;ve created from not posting here for a few years. Since then, the most notable change for me has been my work situation. It&#8217;s changed, but it hasn&#8217;t. Six Apart San Francisco merged with Videoegg to form <a href="http://saymedia.com/">Say Media</a>. I transitioned to Say when that happened. Before that, I had already stepped back about a year or so prior from active work on Movable Type. MT lives on, under the care of Six Apart as it exists today in Japan, where it is in good hands.</p>

<p>Here at Say, I&#8217;ve had opportunity to work on a wide variety of products and services with Python/Django, NodeJS, Objective-C and yes, Perl too. We&#8217;re developing modern publishing tools as well as ad delivery tools (for web publishing, these go hand in hand). Say also owns a number of sites, like <a href="http://readwrite.com/">ReadWrite</a>, <a href="http://splatf.com/">SplatF</a>, <a href="http://remodelista.com/">Remodelista</a> and <a href="http://thekitchn.com/">The Kitchn</a>. One of my colleagues <a href="http://if.andonlyif.net/blog/2013/04/the-future-of-digital-media.html">wrote about what we&#8217;re up to</a> in terms of our direction and focus and sums it up nicely. And <a href="http://www.saymedia.com/careers">we&#8217;re hiring</a> &#8212; if you&#8217;re interested, drop me a line.</p>

<p>And personally, while I&#8217;ve been away from my blog, I have been posting semi-frequently on <a href="http://twitter.com/bradchoate">Twitter</a>, and on <a href="http://pleasefixthat.com/">Please. Fix. That.</a> where I rant about broken things I come across.</p>

<p>Other than that, the wife and kids are doing fine. We&#8217;re enjoying our 9th year in California. We own a house as of a couple of years ago and we have two parakeets.</p>

<p>There, you&#8217;re all caught up.</p>
]]>
        

    </content>
</entry>

</feed> 

