<?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>Jeff Kelley’s Blog &#187; updates</title>
	<atom:link href="http://blog.slaunchaman.com/tag/updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.slaunchaman.com</link>
	<description>Mac tips, iPhone applications, and the like</description>
	<lastBuildDate>Fri, 02 Dec 2011 04:51:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>GCD Example Updated (Now With More Speed!)</title>
		<link>http://blog.slaunchaman.com/2011/08/12/gcd-example-updated-now-with-more-speed/</link>
		<comments>http://blog.slaunchaman.com/2011/08/12/gcd-example-updated-now-with-more-speed/#comments</comments>
		<pubDate>Sat, 13 Aug 2011 04:03:57 +0000</pubDate>
		<dc:creator>Jeff Kelley</dc:creator>
				<category><![CDATA[iOS Programming]]></category>
		<category><![CDATA[Programming Tips]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Cocoa Touch]]></category>
		<category><![CDATA[Grand Central Dispatch]]></category>
		<category><![CDATA[iOS]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[Objective-C]]></category>
		<category><![CDATA[open-source]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[UIImage]]></category>
		<category><![CDATA[updates]]></category>

		<guid isPermaLink="false">http://blog.slaunchaman.com/?p=463</guid>
		<description><![CDATA[Due to popular demand, I’ve updated my GCD example from previous talks to include a few things to make the example not only do something on a background queue, but also snappy. It should scroll much better now. A quick rundown of what changed: Images are now resized. Since the example uses wallpaper-sized images, there’s [...]]]></description>
			<content:encoded><![CDATA[<p>Due to popular demand, I’ve updated <a href="https://github.com/SlaunchaMan/GCDExample">my GCD example</a> from previous talks to include a few things to make the example not only do something on a background queue, but also snappy. It should scroll much better now. A quick rundown of what changed:</p>
<ul>
<li><strong>Images are now resized.</strong> Since the example uses wallpaper-sized images, there’s no sense in <em>not</em> resizing them to go on a 44-pixel-tall table view cell. I’m using the popular image-resizing routines from <a href="http://vocaro.com/trevor/blog/2009/10/12/resize-a-uiimage-the-right-way/" target="_blank">Trevor’s Bike Shed</a> to do the resizing with a nice interpolation quailty.</li>
<li><strong>Those resized images are now cached.</strong> I use an <code>NSCache</code> to store the images. If the app receives a memory warning, it’ll jettison all of the cached images, but if you’re just scrolling up and down this is a quick and dirty way to cache the images. I had never really used <code>NSCache</code> before, so this was a good excuse to try it.</li>
</ol>
<p>I’m at <a href="http://www.cocoaconf.com" target="_blank">CocoaConf</a> in that state down to the South today, so this post has been brought to you by late-night hotel room caffeine. I made some other changes to the project to deal with a weird table view cell bug that I’ve submitted to Apple; a post on that is coming up next!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.slaunchaman.com/2011/08/12/gcd-example-updated-now-with-more-speed/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Apple Surveying 32-Bit Third-Party Kernel Extensions</title>
		<link>http://blog.slaunchaman.com/2011/03/22/apple-surveying-32-bit-third-party-kernel-extensions/</link>
		<comments>http://blog.slaunchaman.com/2011/03/22/apple-surveying-32-bit-third-party-kernel-extensions/#comments</comments>
		<pubDate>Wed, 23 Mar 2011 04:05:44 +0000</pubDate>
		<dc:creator>Jeff Kelley</dc:creator>
				<category><![CDATA[Systems Administration]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Kernel Extensions]]></category>
		<category><![CDATA[Mac OS X]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[updates]]></category>

		<guid isPermaLink="false">http://blog.slaunchaman.com/?p=424</guid>
		<description><![CDATA[Today I noticed something new in my LaunchDaemons folder: /Library/LaunchDaemons/com.apple.third_party_32b_kext_logger.plist. It starts a Ruby script (/usr/libexec/third_party_32b_kext_logger.rb) when your Mac starts up that (and I could be totally wrong, as I don’t know Ruby) appears to use /usr/sbin/kextfind -system-extensions to identify third-party kernel extensions (e.g. kernel extensions for which the identifier does not begin with com.apple) [...]]]></description>
			<content:encoded><![CDATA[<p>Today I noticed something new in my LaunchDaemons folder: <code>/Library/LaunchDaemons/com.apple.third_party_32b_kext_logger.plist</code>. It starts a Ruby script (<code>/usr/libexec/third_party_32b_kext_logger.rb</code>) when your Mac starts up that (and I could be totally wrong, as I don’t know Ruby) appears to use <code>/usr/sbin/kextfind -system-extensions</code> to identify third-party kernel extensions (e.g. kernel extensions for which the identifier does not begin with com.apple) that exist only in i386 or PPC forms. It makes sense why Apple would do this, as a move to 64-bit only would be in keeping with their typical attitude on leaving old hardware platforms behind, but this particular file is odd in that it’s in <code>/Library/LaunchDaemons</code> and not <code>/System/Library/LaunchDaemons</code>, where most Apple-created jobs are. Maybe this was a task given to a programmer new at Apple who was unfamiliar with the typical folder hierarchy on a Mac, but this smells odd. The only result I found for it in Google was <a href="http://discussions.apple.com/thread.jspa?threadID=2791807">this Apple Support forum post</a>.<br />
So, I did some investigation, and found that it uses the domain &#8220;com.apple.kexts.32bitonly&#8221; with the <code>defaults</code> command, and in my system log is this line:</p>
<blockquote><p><code>/var/log/system.log:Mar 22 19:31:30 Jeff-Kelleys-MacBook defaults[3439]: \nThe domain/default pair of (com.apple.kexts.32bitonly, lastRan) does not exist</code></p></blockquote>
<p>That is reason enough for me to believe that it’s installed as a part of Mac OS X 10.6.7, as that message signifies its last run time (the script quits if it’s been less than a week since it last ran). So, being the diligent former sysadmin that I am, I looked at the 10.6.7 update’s files, and didn’t see anything (else) of note. I don’t see a point in the script that reports this to Apple, so I don’t know if this constitutes a breach of privacy on their part, but it’s interesting nonetheless that it would appear that Apple is gauging whether or not they can leave 32-bit kernel extensions behind with minimal customer fuss.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.slaunchaman.com/2011/03/22/apple-surveying-32-bit-third-party-kernel-extensions/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Take Me Home Now Free</title>
		<link>http://blog.slaunchaman.com/2010/05/10/take-me-home-now-free/</link>
		<comments>http://blog.slaunchaman.com/2010/05/10/take-me-home-now-free/#comments</comments>
		<pubDate>Tue, 11 May 2010 04:12:41 +0000</pubDate>
		<dc:creator>Jeff Kelley</dc:creator>
				<category><![CDATA[My Software]]></category>
		<category><![CDATA[App Store]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[shameless plug]]></category>
		<category><![CDATA[Take Me Home]]></category>
		<category><![CDATA[updates]]></category>

		<guid isPermaLink="false">http://blog.slaunchaman.com/?p=267</guid>
		<description><![CDATA[Take Me Home is an ancient, buggy iPhone app that was my &#8220;Hello, World!&#8221; in the App Store. Its sale rate has plummeted to only a couple of buyers a week and, with the prevalence of real, honest-to-God GPS apps in the store these days, its usefulness is questionable. So from here on out, it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.slaunchaman.com/my-software/take-me-home/">Take Me Home</a> is an ancient, buggy iPhone app that was my &ldquo;Hello, World!&rdquo; in the App Store. Its sale rate has plummeted to only a couple of buyers a week and, with the prevalence of real, honest-to-God GPS apps in the store these days, its usefulness is questionable. So from here on out, it&#8217;s free. I can&#8217;t promise to continue supporting it&mdash;especially for new devices and APIs&mdash;so the best I can do may be to remove it from the store in the event that some update breaks it.</p>
<p>Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.slaunchaman.com/2010/05/10/take-me-home-now-free/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Safari 3.2 Feature: Secure Website Identification</title>
		<link>http://blog.slaunchaman.com/2008/11/17/new-safari-32-feature-secure-website-identification/</link>
		<comments>http://blog.slaunchaman.com/2008/11/17/new-safari-32-feature-secure-website-identification/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 15:06:01 +0000</pubDate>
		<dc:creator>Jeff Kelley</dc:creator>
				<category><![CDATA[Mac Tips]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[Mac OS X]]></category>
		<category><![CDATA[Safari]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[updates]]></category>

		<guid isPermaLink="false">http://blog.slaunchaman.com/?p=96</guid>
		<description><![CDATA[Here’s a quick tip that slipped through the blogosphere (at least none of the Mac blogs I subscribe to featured it): in Safari 3.2, released last week, Apple’s added a feature from Firefox 3’s “awesome bar”: when you’re on a secure website, such as a bank’s, that has identification information, it’s displayed in green (though [...]]]></description>
			<content:encoded><![CDATA[<p>Here’s a quick tip that slipped through the blogosphere (at least none of the Mac blogs I subscribe to featured it): in Safari 3.2, released last week, Apple’s added a feature from Firefox 3’s “awesome bar”: when you’re on a secure website, such as a bank’s, that has identification information, it’s displayed in green (though in Safari it’s at the top-right of the title bar).  A screenshot:</p>
<p> </p>
<div id="attachment_97" class="wp-caption aligncenter" style="width: 298px"><img class="size-full wp-image-97" title="Safari 3.2 Title Bar Security" src="http://blog.slaunchaman.com/wp-content/uploads/2008/11/picture-1.png" alt="Safari 3.2 adds secure website information to the title bar." width="288" height="80" /><p class="wp-caption-text">Safari 3.2 adds secure website information to the title bar.</p></div>
<p>Along with <a href="http://www.tuaw.com/2008/11/13/apple-releases-safari-3-2-including-security-updates/">a phishing filter</a>, it looks like Safari is stepping up to the plate as a secure browser.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.slaunchaman.com/2008/11/17/new-safari-32-feature-secure-website-identification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

