Personal tools
You are here: Home Weblog Adding safe MIME types to Epiphany

Adding safe MIME types to Epiphany

Posted by Sean Fulmer at Mar 02, 2008 09:15 PM |
Filed under: ,

or, how GNOME's over-zealous hand-holding nearly ruined a moment of joy

I was pretty excited when I found out that Amazon's MP3 downloader is finally available for Linux. I get most of my music from eMusic, but it's nice to have options :)

I downloaded the deb package, installed it, bought an album, and was immediately presented with a fun dialog similar to this:


Epiphany unsafe file type dialog

JOY. What could have been a seamless, 1-click music purchase was changed into a clumsy series of download/locate/click steps. I can't really blame Amazon for this - it's Epiphany making the safest decision when presented a brand new MIME type, which isn't such a bad thing in and of itself.

(However, GNOME will, without a peep, happily allow me to unleash this file's document-damaging, privacy-invading wrath once I've downloaded it.)

What is a bad thing is that there's no UI in Epiphany to let me decide what's safe and what isn't. Isn't setting up helper apps for file types a pretty common thing? You can't even fix this as a regular user - to add a new safe MIME type to Epiphany, you have to add it to the "safe" section in /etc/gnome/epiphany/mime-types-permissions.xml, which of course requires you to be root.

(In this case, the MIME type for Amazon's AMZ files is <mime-type type="audio/x-amzxml"/>)

GNOME is my desktop environment of choice, and I admire the GNOME project's goal of simplicity, but forcing a user to muck around with XML inside of a system configuration file seems to be contrary to that goal. When you dumb things down to the point where you're removing the means to change common settings, you're going a bit too far.

Like I said, it's nice to have options. :)

Document Actions