A very new word, for a recent phenomenon, and a great example of how technological change, especially that relating to the Internet and the media, can be a driving force not only in generating new words, but in determining whether they survive and succeed. In this case the rapid adoption of podcasting (the technology) as a means of making audio material available has seen podcasting (the word) move quickly from its first tentative steps in 2004, as only one of a number of suggested names for the process, to near-ubiquity in 2008. The current OED quarterly release also includes other members of the same family: podcast as a noun and a verb, podcaster, and even the somewhat ungainly adjective podcasted.
Michael Geoghegan pointed to the provenance of the word, which dates back to a post by Dannie Gregoire in Yahoo group ipodder-dev in September of 2004. Here’s the post with bolding added:
I can see there being the desire of users in some instances to be able
to easily subscribe and get older posts/episodes/shows (what are we
calling these things anyway? How about pode or sode for short?) that no longer
appear on the rss feed. Right now if for example someone wanted to listen to
all the Daily Source Codes back to sode #1, they would have to manually
go through the archives and download any sodes not automagically received,
somewhat defeating the purpose of an ipodder. Not too much of a problem
I guess one could argue that this is simply an rss/server side issue, and that
the “podcaster” (yes, I like making up new words) should be responsible enough
to offer a page of seperate feeds of old sodes by month/year/season/etc.
However, if you have a site with many thousands of sodes this could be very
time consuming and awkward means of getting older content, with no standard
means of organization between different sites. In addition listing gobs
of old contnet could produce a tremendous load on the download servers
getting everything in large batches or all at once.
So first, do we need a more standard means of storing/retrieving older
Second, how to limit the amount of data fed to the user at a time and
prevent server overloading? Is the communication with iTunes two way?
Is there a means of seeing which shows have been listend to by the user?
Perhaps give the user the option of starting where ever in the show’s
history they like then only download x number of hours at a time till
they clean their plate. Then, let them come back for another helping?