a) this is awesome.<p>b) might want to rethink the name. there is a reason closed captions are called closed, and it's to differentiate them from, well, open captions. if this project becomes a big success (and i really, really hope it does) i'd hate to see an increase in confusion for the accessibility community, which has enough trouble getting people to be aware of the different technologies. Go ask an employee at a movie theater showing open captions about open captions. they won't know what you're talking about.
Just wanted to give a shoutout to the first dirty hack using OpenedCaptions: DRUNK-SAPN<p>It is a C-SPAN transcript that gets increasingly drunk. <a href="http://openedcaptions.com/drunk-sapn/" rel="nofollow">http://openedcaptions.com/drunk-sapn/</a>
It's great to see content delivered in an alternative format to engage a different segment of watchers/listeners/readers. Has C-SPAN always provided live transcripts? In layman's terms, how is the data pulled from C-SPAN?<p>Edit: I misread your post. The Opened Captions servers pull CC data in via serial port. Thanks for providing a bridge to this live data.