I just tried to leave a comment in Mark Jen‘s blog. Upon submitting the comment, I got this friendly message:

Spam Karma: Your comment looks suspiciously like spam and has been moderated. It will be displayed once the admin approves it.

Here’s the link to his entry about his invite to Odeo, and below is the comment I tried to leave. Does it look spammy to you?

[…] the most intriguing part was the “Create” button. It claims that they are creating something called “Odeo Studio” which will be a browser-based tool to help you create podcasts. Browser-based?! This could be hot!

Uh, you mean they’re going to create a DHTML page with AJAX that has some form input fields and spits out RSS with enclosures for people to cut-and-paste into a file then upload to their server? Yes, I’ve been thinking about creating such a page but the folks at Red Square have already created Podifier which fills this niche, although it’s not browser-based — it’s a Win32 app.

I’ve been thinking about podcasting, and making it more accessible by lowering the barrier to entry lately, too. New product idea:

1. Instruct podcaster to upload digital media to Ourmedia.
2. DHTML page with form inputs to gather metadata about podcast.
3. Publish podcast feed with URL pointing at the asset now hosted by Ourmedia/Internet Archive.

Result? Free podcasting — at least, free to the podcaster. Ourmedia picks up the bandwidth tab, and podcasters are presented a simple interface for publishing their podcasts. They only need to learn how to upload their content to Ourmedia and use web form.

Sad: there’s probably VC money earmarked for a company that’ll do just this. Ridiculous. Who said the dot-com bubble had burst? Ha.

Bob Parsons, the CEO and founder of GoDaddy.com, shares his 16 rules, informally titled “They Can’t Eat You”. I see Bob as one of my role models and this list is a concise demonstration why.

Mike Duffy shares a list from Bill Swanson, CEO of Raytheon, called “Swanson’s Unwritten Rules of Management”. Apparently he’s giving the commencement speech at Cal Poly for 2005 — I wonder if his speech will be published like Steve Jobs’ was.

In case you’ve been living under a rock for the past year, you’ve probably heard something about podcasting, a term coined by Adam Curry back in 2004. The name “podcasting” is actually a bit of a misnomer, as it implies something that might require owning an Apple iPod, but podcasting really refers to the process of publishing digital audio, accompanied by metadata expressed in RSS to syndicate the content so that software can automate the download of the content. Pointing such software at the podcast RSS feed and instructing it to download new content when it is published is known as “subscribing to the podcast” — the idea is that with an always-on broadband connection to the Internet, you could use podcast client software such as iPodder, which will periodically poll the various RSS feeds and “notice” when new content is available and download it. This way, when you want to listen to the content, rather than having to wait as it streams in real-time over the network, you can play it like any other digital media on your hard drive, since that’s exactly what iPodder will do, download the podcasts and store them on your hard drive. The logical next step is to then synchronize your portable music player, such as an iPod, with this newly downloaded content, so that you can listen to it wherever you like. This is presumably where the podcasting moniker came from — the idea that you could remotely broadcast content to an iPod, or podcast it. I’m not sure if the cuteness factor of the name outweighs the initial confusion it creates with folks new to the term, but I think the term is here to stay, so it’s better to just educate folks on what it means.

With the introduction of excellent software like iPodder, which is free software available for Windows, MacOS X and Linux, it’s become easy for the average user to subscribe to and enjoy podcasted content. But, what if you’d like to publish your own podcasts for others to listen to and enjoy? Well, the folks at Red Square have created Podifier, which is also free software, which simplifies the process of creating the RSS metadata which is used for syndicating the audio content — the software makes it easy to create your podcast feed. This solves half of the whole podcast publishing problem, the other half being finding a place to host both the audio content and podcast feed data. The typical free web hosting available is geared towards hosting HTML which is plain text and generally doesn’t require much bandwidth. Digital audio, on the other hand, requires much more bandwidth — so, your average free web hosting company may not be adequate for hosting your podcast. I see this niche as a great opportunity for companies, just like Flickr has gone after the digital image hosting space.

I hope you’ve found this explanation useful, and maybe you’ll check out a few podcasts or even publish your own!

Tags: podcasting, ipodder, podifier, rss, free software, adam curry, ipod

It’s June, which means it’s graduation time in the US. Mike Duffy delivers an incredible commencement speech at his daughter’s grammar school, the Sonoma County Day School (SCDS). It is one of the best commencement speeches I’ve read, ever, and this was for a grammar school graduation — you don’t see this quality of message at the college graduation level, even.

Let me back up for a second: I originally wrote that last sentence on June 11th, when Mike Duffy posted his speech. A few days later, on June 14th, Stanford posted the commencement speech that Steve Jobs gave on June 12th. Indeed, if I had to decide between Mike’s and Steve’s speeches and say which is better, I don’t think I could. They’re aimed at different audiences, as Steve’s audience has already made the large investment in a Stanford education, as opposed to the SCDS graduates who still have between four and eight or more years — assuming they continue on to college or beyond — of school ahead of them to do something with themselves. Both messages are relevant, meaningful and well-delivered. I’d recommend that everyone give both speeches a good read and decide for yourself which one speaks to you more, and take it to heart.

Mike Duffy and Steve Jobs have really managed to capture the essence of what is important to focus on and expressed it in a very emotionally accessible way. I hope those kids from Mike’s daughter’s school go on to do great things, and they will, if they remember that all things are possible because we make the rules. I also hope the kids from Stanford realize that all the money and college education in the world won’t amount to anything if you don’t follow your passion, even if it isn’t obvious why you should be, because history will tell a different story about your life than you think it will.

Update 2006-06-08: Stephen Colbert and more great commencement speeches of 2006

Tags:
inspirational,
graduation,
speeches

<p><a href=”http://archive.scripting.com/2005/06/20#When:8:42:37PM”>Dave Winer</a> is <a href=”http://www.opml.org/spec”>OPML</a>’s biggest cheerleader, for obvious reasons. He mentions that <a href=”http://www.steve-lacey.com/blogarchives/2005/06/podcast_shownot.shtml”>Steve Lacey thinks podcast shownotes should be RSS</a>. I think Dave’s right in that Steve’s approach is wrong, but I think Steve’s right that <a href=”http://blogs.law.harvard.edu/tech/rss”>RSS</a> is the answer, not OPML.</p>

<p>Here’s my take on it: suppose each podcast is treated as its own RSS <channel>. Suppose each “segment” within the podcast that there are notes for is treated as its own RSS <item>. Suppose we adopt the convention for audio URLs that named anchors of the form “[[hh:]mm:]ss[.xxx]”, or hours, minutes, seconds, and milliseconds from the start of the audio. (I’m not sure I really like this format. Perhaps a simple integer number of milliseconds would be better.) So, an example RSS for a fictitious podcast might look like:</p>

<xmp style=”overflow: auto;”>
<rss version=”2.0″>
<channel>
<title>Some Podcast: June 21, 2005</title>
<link>http://www.example.com/link-to-this.xml</link>
<description>
Some descriptive copy about this podcast in general.
</description>
<item>
<description>Notes for this segment of the podcast, starting at 0 sec.</description>
<enclosure url=”http://www.example.com/path-to-podcast.mp3#0″ length=”8675309″ type=”audio/mpeg”/>
</item>
<item>
<description>Another segment, starting 1 minute, 28 seconds in.</description>
<enclosure url=”http://www.example.com/path-to-podcast.mp3#1:28″ length=”8675309″ type=”audio/mpeg”/>
</item>
</channel>
</rss>
</xmp>

<p>This approach would require no change to the RSS specification, unlike Steve’s approach; it would just require applications that process RSS to understand the URL correctly, and those that haven’t been updated will degrade gracefully if they parse URL’s correctly and ignore the anchor portion. One downside of this approach is only being able to specify the starting offset and not the length of the segment, though.</p>

<p>If we <b>are</b> going to change the specification in order to introduce this capability, my preferred solution would be to extend the <enclosure> tag to introduce two new attributes: startOffset, endOffset. For simplicity, these would be integer values in number of milliseconds as offsets into the audio stream. Again, this is simple and straightforward, and backwards-compatible if older applications degrade gracefully and ignore the attributes they don’t recognize.</p>

<p>Hopefully, someone out there will see this rambling and give it some thought.</p>

I finally got sufficiently motivated to implement a comments RSS 2.0 feed. It updates every 60 seconds and contains the 15 most recent comments. Add it to your news aggregator, or subscribe to it at Bloglines.com. Oh, and if you haven’t added the entry feed, do that too (at Bloglines.com).

Magnus Daum and Stefan Lucks publishes Attacking Hash Functions by Poisoned Messages, “The Story of Alice and her Boss”, which gives a meaningful explanation why being able to identify two messages that share the exact same MD5 hash in a reasonable amount of time renders MD5 no longer useful for providing message digests.

I just can’t help but laugh at what could have been a potential title and by-line for this article: Finding two PostScript documents with the same MD5, by Daum/Lucks. Juvenile — I know — but I still think it’s funny.

(via Bruce Schneier)