MP4 in Python-iView

26 December 2009

G’day Python-iView’ers. As you might know, the ABC has been transitioning to MP4 (with H.264 video) for a lot of their videos.

iview-gtk doesn’t yet support it, but here’s how to do it with iview-cli. First, find an MP4 video:

$ ./iview-cli --programme
[...]
Compass Series 23:
	Compass Series 23 Episode 47	(compass_09_23_47.mp4)
[...]

Then, download it like so:

$ ./iview-cli --download mp4:compass_09_23_47

So, basically, strip the .mp4 off the end, and add mp4: at the beginning.

The pattern seems to be slightly inconsistent, so I haven’t been able to code up something to do it automatically, but once I figure it out, I’ll make it all automagic for you. This is just something to use in the meantime.

Hope this helps.

Mandatory filter (Clean Feed) trial results announced

16 December 2009

Well, it’s official. Conroy and the DBCDE (hey, that could be the name of a band!) have released the results of the much-debated Clean Feed.

From the pretty performance graphs in the report, the filter doesn’t appear to be performing too badly. Implemented correctly, this filter could be put to use without a major impact on performance. However, that’s missing the point!

The point being that with the filter in place, it is basically equivalent to being wiretapped all day every day. Wiretapping in itself is not bad — it is sometimes plays an important role in solving crimes, or thwarting conspiracies. However, all wiretapping to date requires prior evidence of criminal activity, and a warrant is needed to perform it.

This “clean feed” is effectively wiretapping without a warrant. In other words, treating the general public like criminals. Guilty until proven innocent.

Once you establish that, how well the filter performs is a moot point. Admittedly, it is entirely possible BGP will be used so that only certain websites will be run through the filter (i.e. selective proxy). However, there is no guarantee that this technique will be used, and it is only a technical difference — the legislation to implement would be exactly the same. So the government could effectively change at will to monitoring all web traffic.

One quote I found interesting from the report:

Telstra reported that heavy traffic sites could overload its trial filtering solution if included in the filtering blacklist. This is also the case for all filters presented in the pilot.

So basically they are admitting the filter will be vulnerable to denial-of-service attacks. This could be exploited by criminals around the world with access to large botnets. Not only that, but a large amount of personal information is still transmitted over HTTP. Though unencrypted, the links between me and the website I am exchanging with are largely trusted. However, putting a filter in the middle that is explicitly designed to read the information suddenly makes the situation far scarier.

I also found no mention of IPv6 in the report. Because the trial has been reported to depend heavily on proprietary software, no mention of IPv6 is made, and of which it is common knowledge that proprietary software is more often than not lagging behind in cutting edge technologies, it is entirely likely that the filter will: (a) possibly hinder IPv6 adoption by ISPs, (b) cut off access to IPv6–enabled sites, or (c) be ineffective at blocking sites that are accessible via IPv6.

Python-iView updated to iView 316

1 December 2009

I’ve updated Python-iView to support the latest iView version, 316. To get the latest update, change to your python-iview directory, and type:

$ bzr pull

In this update:

  • New programme API supported, which permits faster loading times.
  • The entire programme is no longer loaded. Instead, the individual series are loaded when you select them in the GTK+ interface, making for faster startup times.
  • SWF verification keys updated.
  • RC4–encrypted programmes supported (was required in version 306, though subsequently disabled by the ABC again and made unnecessary).

Here is a roadmap for what I would like to achieve in the next couple of releases:

  • GIO–based saving (e.g. so you can save into an SFTP share).
  • Ability to run from read-only system directory (the previous point is a prerequisite for this), and packaged into .deb or .rpm format for easy installation.
  • Category browsing, thumbnail display, and metadata such as ratings, duration, size, etc.