<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Kyle Dent on O&apos;Reilly Broadcast</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/" />
<link rel="self" type="application/atom+xml" href="http://broadcast.oreilly.com/atom.xml" />
<id>tag:broadcast.oreilly.com,2008-08-07://53</id>
<updated>2009-11-13T05:38:07Z</updated>

<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<entry>
<title>BigShot Camera Educates with DIY</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/bigshot-camera-educates-with-d.html" />
<id>tag:broadcast.oreilly.com,2009://53.38492</id>

<published>2009-11-13T05:38:07Z</published>
<updated>2009-11-13T05:38:07Z</updated>

<summary>Shree Nayar, chair of Computer Science at the Columbia University has created BigShot, a digital camera kit for kids from eight years old and up to construct their own digital cameras. The purpose of the camera is primarily education, and testing indicates that it does a good job at that, but it also takes honest-to-goodness photos just like grown-up, pre-assembled adult versions.</summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="digitalphotography" label="digitalphotography" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="education" label="education" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Shree Nayar, chair of Computer Science at the Columbia University has created BigShot, a digital camera kit for kids from eight years old and up to construct their own digital cameras. The purpose of the camera is primarily education, and testing indicates that it does a good job at that, but it also takes honest-to-goodness photos just like grown-up, pre-assembled adult versions.
</content>
</entry>

<entry>
<title>Recursively edit files with sed</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/08/recursively-edit-files-with-se.html" />
<id>tag:broadcast.oreilly.com,2009://53.37708</id>

<published>2009-08-11T21:02:37Z</published>
<updated>2009-08-11T21:02:37Z</updated>

<summary>Well duh, that&apos;s exactly what sed is designed to do. And nowadays most implementations have the handy -i option that makes changes in place without explicitly using an interim file. Which means that I could reduce the work of typing in the Perl script to a single line at the command prompt...</summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="find" label="find" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="sed" label="sed" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="unix" label="unix" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Well duh, that&apos;s exactly what sed is designed to do. And nowadays most implementations have the handy -i option that makes changes in place without explicitly using an interim file. Which means that I could reduce the work of typing in the Perl script to a single line at the command prompt...
</content>
</entry>

<entry>
<title>Obscuring Email Addresses Actually Works</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/07/obscuring-email-addresses-actu.html" />
<id>tag:broadcast.oreilly.com,2009://53.37587</id>

<published>2009-07-25T02:36:23Z</published>
<updated>2009-07-25T02:36:23Z</updated>

<summary> I&apos;ve always wondered if obscuring email addresses on web pages does any good, for example writing &quot;bob at example dot com&quot; instead of displaying the actual email address. It turns out it does </summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="email" label="email" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="spam" label="spam" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
 I&apos;ve always wondered if obscuring email addresses on web pages does any good, for example writing &quot;bob at example dot com&quot; instead of displaying the actual email address. It turns out it does 
</content>
</entry>

<entry>
<title>Technology Innovation Site Will Launch in the Fall</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/07/new-site-advancing-innovation.html" />
<id>tag:broadcast.oreilly.com,2009://53.37575</id>

<published>2009-07-23T17:26:59Z</published>
<updated>2009-07-23T17:26:59Z</updated>

<summary>The Henry Ford, the museum associated with Henry Ford and his company, will be launching a new web site focusing on recent innovation and the people who make it happen.</summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="announcement" label="announcement" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="innovation" label="innovation" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="technology" label="technology" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
The Henry Ford, the museum associated with Henry Ford and his company, will be launching a new web site focusing on recent innovation and the people who make it happen.
</content>
</entry>

<entry>
<title>Using Ajax and Search Referrer Info to Help Users Navigate Your Site</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/07/post-4.html" />
<id>tag:broadcast.oreilly.com,2009://53.37543</id>

<published>2009-07-19T00:17:49Z</published>
<updated>2009-07-19T00:17:49Z</updated>

<summary>Using the referrer URL to detect what brought users to your site can let you help them find what they&apos;re looking for. The almost magical asynchronicity of Ajax lets you provide additional content for users from search engines. It requires only minor changes to your site and doesn&apos;t affect the experience for others.</summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="ajax" label="ajax" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="javascript" label="javascript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Using the referrer URL to detect what brought users to your site can let you help them find what they&apos;re looking for. The almost magical asynchronicity of Ajax lets you provide additional content for users from search engines. It requires only minor changes to your site and doesn&apos;t affect the experience for others.
</content>
</entry>

<entry>
<title>Postfix Postscreen to Increase Your SPF (Spam Protection Factor)</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/07/postfix-postscreen-to-increase.html" />
<id>tag:broadcast.oreilly.com,2009://53.37456</id>

<published>2009-07-07T20:59:28Z</published>
<updated>2009-07-07T20:59:28Z</updated>

<summary>Postfix is about to add a new tool to the anti-spam arsenal called &quot;postscreen&quot; for now, but the name is likely to change before it goes into a production release. Among other things postscreen detects when a client starts talking before it&apos;s supposed to. It&apos;s a daemon that accepts connections ahead of the current SMTP daemon and provides various types of filtering based on the client connection. </summary>
<author>
<name>Kyle Dent</name>

</author>

<category term="email" label="email" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="postfix" label="postfix" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="spam" label="spam" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Postfix is about to add a new tool to the anti-spam arsenal called &quot;postscreen&quot; for now, but the name is likely to change before it goes into a production release. Among other things postscreen detects when a client starts talking before it&apos;s supposed to. It&apos;s a daemon that accepts connections ahead of the current SMTP daemon and provides various types of filtering based on the client connection. 
</content>
</entry>

</feed> 