Yeah, I could do that easily enough but it's money I'd rather not spend. DVDs are kind of dead media now, that's where this branch of the discussion originated. I skipped the whole BD hardware era because BDRips are easy enough to find online. I used to do a lot of DVD mastering with DVD Studio Pro but I haven't touched it in years, everyone wants files for online delivery now. For the rare occasions I would ever need a DVD drive, the kludgy Remote Drive is good enough.

Well that's another problem right there. My mini doesn't have a DVD drive, if I want to rip a DVD I have to use Remote Drive and link to my old G4 Windtunnel machine, the last machine I owned with an internal DVD drive. So I usually just copy the VOB to my local Mini and transcode it there. I don't know if that is any faster or slower, I have nothing to compare it to, I haven't ripped a DVD in years probably. In transcoding, Handbrake will peg the CPU but I don't recall exact fps, something around 100 I think. It's an old dual core i7, it's no speed demon. Jeez, I remember when I got a PowerPC G5 and I thought it was a fucking miracle that I was able to encode mpegs for DVDs in just a bit faster than 1x realtime. The G5 would kick out so much waste heat, my office temperature would get up to over 100F.

It would be difficult to judge by my encoding times, I'm using an antique Mac mini 2011 model with a 2.7Ghz i7. I have an SSD but encoding is CPU intensive so the CPU is the bottleneck. I haven't done any direct comparisons at similar encoding rates, the Compressor settings are so dissimilar that I'm not sure how I'd even compare them to Handbrake. But overall Compressor seems more flexible and faster. Apple pro apps tend to use multithreading very efficiently so they're fast on multicore computers like mine (i7 with 2 real cores, 4 virtual cores).

Be fair, it does a good job of transcoding. I tried using the previous version of Handbrake to transcode some video files that wouldn't play on my iPhone, it was good enough. But I use a Mac and the feature to add a batch of files all at once is missing from that version, so it was a bit inconvenient to set up a big encoding run one file at a time. Maybe they added it to this release. But ultimately since I'm on a Mac and I have Final Cut Pro, it's faster for me to use Compressor.app.

Check out the player experience, and its navigation, commentary, captioning, etcetera. And it uses Smooth Streaming to provide proxy-cachable video at multiple bitrates.

As he said, those features are all available on the video players already available. QuickTime and QuickTime Streaming Server (and it's Open Source version Darwin Streaming Server) already offer all those features.

So why do I need Silverlight, except to support Bill Gates' attempt to "knife the baby"...?

Correct. There is no way to put a Public Domain book back into copyright, except through translation (that would be a new, original derivative work). Just re-typesetting the text does not create a new copyright. Mazzone's paper describes in detail "copyright creep" where authors slap a new foreword onto a PD work and then claim a fraudulent copyright on the whole book. Yes, the foreword would be copyrighted but the other contents could not be copyrighted.

A useful analogy, but it's worse than that. It's kind of like someone building a superhighway through your backyard. Let me give a specific example.

I used to participate in an alt.binaries group, we traded fairly obscure music (mostly out of print) and it was a low traffic newsgroup (not in the mp3 hierarchy), so even the top Usenet ISPs wouldn't give it much storage space. So we had a generally agreed-upon posting method, no flooding and each person would restrict their posts to about 500Mb per day. We judged that most of the top ISPs gave the newsgroup about 5Gb of file space, so files never expired from old age, they were always pushed off the server. When we limited flooding, posts would last about a month on the server, when everyone posted faster, they expired in about a week. That seemed adequate, everyone was happy, and if files expired early, most users were happy to repost on request (although more slowly a second time).

So after a few go-rounds with FTDers dumping 1Gb floods, and everybody getting pissed off, some FTD asshole starts a 10Gb flood. Regular users are posting a few albums of maybe a dozen files, and their first file is pushed off the server before the last one is even done posting. The FTD idiot isn't even aware that he is flooding off his OWN files, the first 5Gb is being pushed off the server by the last 5Gb. Now THAT is really goddam stupid.

Obviously the FTDers are not aware of common Usenet limitations. They think a Usenet nntp server has unlimited resources, but it doesn't. In an ideal world, every nntp server would have infinite storage space, that is impossible, but it's a basic assumption of the FTD system. They treat Usenet as an infinite resource, they can dump an infinite amount of files anywhere and they expect the system to handle it. I've seen even worse abuses, some FTD asshole will pick some obscure binaries group and use it to dump off-topic files. It doesn't matter where you post an FTD file, you could post mp3s in alt.bestiality.hamster.duct-tape and the FTD servers would locate it just as easily as if it was in alt.binaries.sounds.mp3.* since their system is designed to handle locating the files. It's indexed on their servers, not under topic categories by newsgroup. They'll dump files anywhere they like, and are answerable to no-one. This has ruined several newsgroups and driven people away from Usenet.

Fuck The Dutch.

Oops, should have previewed and edited that again, of course it is RTSP (Real Time Streaming Protocol) and I always mix it up as RSTP.

Streaming QuickTime has been a continual subject of discussion on the QuickTime Streaming Server listserv. Note that I am not referring to progressive download QT, I'm talking about RSTP streaming. Services like YouTube have the ability to detect the maximum bandwidth of the receiving device and deliver a stream encoded for that bitrate. In YouTube's case, they have a custom app that detects whether you're on EDGE or WiFi and delivers a progressive streaming file of higher or lower quality. I have been dissatisfied with the YouTube service, it seems to always stream poorly. And you have to wait and wait for enough of the file to load before it will start playing. Usually my iPhone (even on WiFi) goes to sleep and shuts off long before I can start watching, which aborts the download.

What the QTSS listserv people are all begging for is true RSTP streaming from QuickTime Streaming Server to the iPhone in Mobile Safari, and an API for apps. QTSS detects your device's bandwidth and delivers a true stream with the appropriate bitrate so it can begin playing instantly, and if you drag the playback slider to any point in the file, it begins playing instantly from that point. This would be a huge advantage, but there is a downside. Since the stream is being delivered continuously on demand, you can't deliver higher bandwidth (higher quality) files that would take a while to download. The file's bitrate may be no more than the channel would allow. But us QTSS users think this is an advantage, I would gladly trade off a little quality for instant-on playback. Another advantage is that QTSS can deliver live video from QuickTime Broadcaster, so live TV events can be delivered live.

The upshot of the deal is, Apple has not yet enabled RSTP in the iPhone, so it is not available in apps like Mobile Safari. I personally believe (without any evidence) that this is Apple's attempt to cripple Mobile Safari so as to not antagonize AT&T by overloading their network with streaming video. But there are some apps that have RTSP streaming now, there's an app that streams college radio stations (I forgot the name of the app). I don't know how they got it to work, they must have their own RTSP code, it's not in any current iPhone 2.0 OS API.

I have been telling people for years, if you wanted to start a new TV delivery method, all you'd have to do would be roll out a new line of smartphones with adequate data capacity and live streaming like QTSS. You could start another major network overnight. I've found the quality of TV watching on my iPhone (from my own manually encoded files) to be perfectly fine. But Apple won't enable RTSP on the iPhone... yet. Maybe they have something coming in iPhone OS 3.0, but there hasn't even been a hint of this capacity. Plenty of people are filing the request with the appropriate Apple people, and we get no response whatsoever. Let us hope that no news is good news, and they are not leaking or hinting at anything because they are under an NDA because it's about to roll out.

FTD is doing horrible things to usenet, they're a plague on any newsgroup they descend upon. FTD makes software so people can use Usenet as a P2P system without ever interacting with the newsgroup. This has not been popular with most newsgroups that have standards for posting. FTD does things their way, and when massive complaints from newsgroup participants are posted, the FTDers never see them. I've seen newsgroups destroyed by floods of FTD posts. The regular participants (the most valuable members of the newsgroup) have their contributions buried by massive floods of off-topic posts. And there's nothing you can do to stop them.

On most usenet groups, FTD is commonly parsed as "Fuck The Dutch." They want to exploit Usenet for their own ends without participating in Usenet culture. Fuck em.

While this may be the first game for a 16-bit personal computer, I don't believe it is the first game for any personal computer.

I will offer a more likely contender: TARG for the Processor Technology SOL-20. I recall typing this game (and several others I've forgotten) into my SOL back in 1975. TARG became available commercially on a cassette called GAMEPAC 1, I just happened to have the GAMEPAC 1 manual sitting here and it's copyrighted 1977.

Since the article claims sometime in 1975 as the "release' of Space War, it is probably going to be difficult to pinpoint exactly which app was written first, they appear to date to almost exactly the same time. But since Space War was a one-off production for a unique custom computer, it hardly had the impact of an app like TARG that was widely available on a commercially produced personal computer (that came as a kit or pre-assembled).

In case you're interested in TARG, it was a dart throwing game done entirely in text mode, with animated graphics. IIRC you used keys to move a cursor up and down and the space bar to toss a dart at a target. A little custom character flew across the screen. I'm restoring my SOL now and TARG is the program I'm trying to get to run first. The CPU is working but alas my RAM boards are dead so there's no memory space to run even small apps.

That's the worst (and most totally incorrect) description about the early history of the movie industry I ever heard. And I've heard a zillion of them, since I worked in Hollywood for many years.

Obviously you are confused about the origin of the patented Edison cameras. There was a format war and Edison owned the basic patents on standardized film cameras that worked with the movie projectors in all the theaters. Some people tried to issue cameras in the Edison format that didn't pay Edison royalties. Others tried to start a new format, with predictable lack of success.

If you're going to argue a historical point, you should at least make a MINIMAL attempt to get the history right. I'm no fan of Edison (who often acquired patents in ways that we would now call him a "patent troll") but that doesn't make the early history of the Movies anything more than a plain old patent infringement problem. Without Edison's corporate backing of a standard format, movies as a medium would have been delayed in development and might never have taken off as a popular entertainment. You can try to recast that as a the activities of Robber Barons, but you're not being the least bit objective about that.