After even Apple fixed their software to reject certificates issued by Diginotar, Android is (one of?) the last platform that did not issue a fix. Given the fact that this whole affair started, because Google users' confidentiality was compromised by the Iranian government using a false certificate from DigiNotar, this is quite surprising.

Update: Fix now available in update.zip format. All current Android phones have IPv6 enabled by default, which means that as soon as you connect to an IPv6 enabled network (e.g. via Wifi) you will start using IPv6 with an IP address that reveals your MAC address of your network interface.

This is a bugfix release fixing several problems in previous versions. It is highly recommended to upgrade.

Changelog of this release:

• Bugfixes to the replace_map function. Previously, no recording could be found when a title was changed. This is fixed now.
• Bugfixes to the delete function to prevend deleted recordings to reappear in the folder listing when the cache is refreshed.
• Proper support for international language support. utf-8 is tested, latin1 only partially (send in your bugs!).

I released a new version of mythfs with an improvement and a new feature:

• Improved version of the delete function: it turned out that a recording stayed in the database for several seconds after it was deleted through the mythtv native API. Therefore, the program still appeared in the listing even after a refresh. I now keep track of deleted items for the duration of the CACHE_MAX_AGE. This way, programs will not appear anymore after they have been deleted.

It has been a while, but here's a brand new release of mythfs. From now on Mythfs release numbers will be synchronised with the Mythtv releases, so you can easily download the version matching your backend.

The main changes are:
1) Support of all recent MythTV versions (up to 0.24). Mythtv protocol version up to 65 are supported, including the new (crazy) release tokens

A new version of MythFS. Besides a lot of code improvements, this version supports the deletion of recordings. The recordings will be deleted by communicating with the native protocol to the MythTV backend. Therefore, MythFS now speaks the native protocol.

This little tool can be used to make MythTV recordings easily accessible to
programs without implementing any interface towards MythTV, because each
recording is just a file. After mounting the filesystem, a virtual directory
structure is created with 3 top entries: Programs, Dates and Channels. All
recordings appear as directories and files in this tree. Currently, the only
operations supported are:

• browsing the directory tree
• reading individual recordings
• deleting recordings (for protocol versions 40 and 44)