I really like the idea, but there are some implementation problems I haven't yet seen addressed. I'm very much in the target market (web designer / developer),

I really like the idea, but there are some implementation problems I haven't yet seen addressed. I'm very much in the target market (web designer / developer), and I'd like very much for this to work, but I just don't see it. Here's my issues / questions, would be interested in hearing why I'm wrong: - The fonts available on typekit aren't the ones I want to use. Without support for the Linotype / ITC / Adobe fonts, I'm left choosing a font from what you do offer, and at that point I might as well just choose a free one and host it myself. Any plans to get the big-name foundries on board? FWIW, the fonts I most often need this for are the various flavors of Helvetica, Gotham, Trajan Pro, and Myriad Pro. - The main benefit to cufon/sIFR/etc is that it works with all browsers, specifically those that don't support @font-face. This doesn't solve that problem. I know typekit falls back to standard fonts, but I can do that. - I usually avoid fancy fonts in all but headings and other large elements. If the text is static its not a big deal to save the text in Photoshop and use text-indent to replace the plaintext. Dynamic text, like blog post titles, is a pain in the ass, but cufon / sIFR handles that case well enough. - Its one more server and one more fee added to the equation. Furthermore, I don't have enough confidence in this business model to trust the service to remain around forever.