FAT32: no POSIX metadata, 4GB file size limit is deadly. It's inefficient, and generally outdated and nasty.
NTFS: proprietary, sometimes complicated to get on Linux, hard to get on OSX.
ext*: bad-to-none support on non-Linux. IIRC, neither the Windows nor OSX drivers support journaling, for example.
HFS+: about the same boat as ext*, if you swap "Linux" and "OSX".
UDF: reasonably efficient, support for basic metadata (POSIX, though no EAs or forks), full support on Linux 2.6, OSX 10.5, Windows Vista/7, or (with third-party utils)
argue my way up the manager food chain
What you fail to understand is that the customer-accessible part of the manager food chain in the vast majority of companies is approximately two people tall: CSR and supervisor. (Depending on the company and nature of question, you may be able to get to tier2 support; hence the "approximately".)
You will have better luck...
Maybe because it's decent in suburban areas, because it's significantly cheaper than AT&T, Sprint, or Verizon, because we don't mind roaming, and because T-Mobile is slightly less obviously run by assholes than the other three aforementioned companies?
Let me elaborate a bit on a previous comment.
T-Mobile's ETF is $200. They can't offer you a subsidy of significantly more than $200, because then it would be to your advantage to buy a phone, cancel your contract, and sell the phone for a profit. Contract lengths are two years. Amortized over 2 years, by taking the subsidy, you save $8._33. Meanwhile, T-Mobile's has two tiers of plans. One gives you the subsidy, has a contract, and is $10 more a month. Thus: if you have the money up-front, buy your phone, save $240 in the cost of a plan over two years, and save yourself from a contract.
Consider the Motorola Cliq. As a user, it's a good phone.
but they haven't even bothered to make sure that only leaf certificates can be issued.
Nope; the CA only signed a what you call a leaf certificate, but the constraint which determines whether a key can is a branch ("CA = true") or leaf ("CA = false") was part of the cert that they were able to change. See the last paragraph of section 5.1
A computer scientist is someone who fixes things that aren't broken.