Are they distributed with "http://" despite not following that protocol? I don't know what goes into making a new protocol specifier, but if podcast thingy is a protocol that we like then maybe we ought to do something like podcast:// so the right app can be summoned rather than having your browser do its best.