Jon Udell has been "quoting" audio and video snippets on the web for some time.
It is presently a very difficult process, but Jon's approach does not need a server to capture any media. He just hyperlinks to a media file and gives it start and end points.
"Speaking of quotes, I have a question. Although we often create or follow links to streaming audio, these usually refer to entire streams. I rarely see parameterized URLs that pinpoint specific quotes, analogous to the way we use fragment identifers in HTML pages to isolate paragraphs. Why not?"
"There's something missing from the audioblogging experience, though, and I've written about it before: audio is a more opaque datatype than it ought to be.
We routinely quote fragments of text, and although the tools available for doing so leave a lot to be desired, it's something most people can figure out."
"The issue I want to highlight is the gap between what technically proficient users of the blogging medium (or indeed any kind of web authoring) can achieve, and what average users can achieve. Ironically the best way for me to make that point -- by citing portions of the webcast -- is yet another illustration of the problem. In several different sessions [at BloggerCon], people made compelling pleas for simplicity. It ought to be easy for me to send you to those places in the webcast. It isn't."
"To broadcast a stream, you point QuickTime broadcaster at DSS, export an SDP (session description protocol) file from QuickTime BroadCaster, and place it in the streaming server's Movies directory. To view the stream, launch QuickTime Player and load a URL like rtsp://dss_host/broadcast.sdp. Once I got this working I moved the server to a second DSL circuit in my lab. I configured the firewall to allow TCP ports 80 and 544, and UDP ports 5432 and 5434. And amazingly, it all worked. From my TiBook on one Internet-connected private LAN, I was streaming video to a server on a different Internet-connected private LAN. That server's broadcast was available -- at an eight-second delay -- to any QuickTime Player on any platform anywhere on the Internet. What's more, the TiBook could be sending the stream from any Wi-Fi-equipped meeting or conference, anywhere on the Internet."
"Minutes-and-seconds notation. In the index file you can write URLs in terms of minutes-and-seconds, not the byte-range lingo that the client and server speak. These URLs aren't available outside that context, though. And while it's possible to package up the start/stop syntax into a .ram file that you can point a browser at, you can't (so far as I know) form an URL that indexes into the SMIL assembly."
Here are a few examples of quotes from Jon Udell's session on Aggregators at BloggerCon 2003, using the technique Jon explained in his October 8 column above.