Yes. In the end I had to contact Tumblr and have them take a look. They told me my feed was fine and they had to reimport it from their side to get it to work. No documentation.

No, but I have done some XML->RSS->Tumblr work and found out how brittle Tumblr is.. I'll work on this when I get time and post about it.

No. If I'm willing to part with a bunch of money, there are a few good solutions. I think Softbank will eventually come out with a micro SIM card, but they are severely lagging. Once I do decide on something, I will update this post..

The voice options here are horrible, but I think I can grab a prepaid at the convenience store and take a scissors to it.. In the meantime, my 415 number will almost get to my phone (will text me).

This was the issue I was having getting this to build, so it has nothing to do with your modifications. Since I'm using a non-standard OS X SDK, I didn't seek outside help and tried to track the problem down myself... and failed.

I think compiling with a different version of GCC might help, but I'm more interested in get Clang working. If you figure this out, let me know. And if you are using standard tools, I might jump back in to try to debug.

Please keep us updated.

Thanks for the comment. I never said Apple was stupid and was not being sarcastic with any of the comments regarding Apple. They are taking a pragmatic approach to the situation and I would expect nothing less of them.

As a licensee of the technology, Apple can toss H.264 into Safari and not have to worry about anything. If they went with WebM, there are the potential of submarine patents or a new patent pool by the MPEG-LA. MPEG-LA would much rather go after an Apple or a Google than a Mozilla.

What I fail to mention in this piece is that any company that provides the coder or decoder in their product has to pay royalties. These royalties would then pass along the FOSS chain as forks could not become sublicensees, they would have to license directly with MPEG-LA. With this new (to me) information, Mozilla is taking the only route available to them - WebM.

I'm not sure if Apple's adoption of H.264 is going to cause the negative externalities you mention. They could join with Microsoft in tossing H.264 out the window and standing up for WebM, but what is there to gain by that? If I were a shareholder of either company, I would expect them to do exactly what they currently are doing, supporting H.264.

What version of apxs are you using?

Thanks.

And you're not the only one who has contacted me about the Tumblr function. I don't think it exists so I'll whip up a plugin this weekend or so..

It's the build configuration if you want to compile Firefox yourself. If aren't going to compile, you don't need that file.

I think this is a problem with the Google infrastructure. Just as you get different results from search from different locations or even the same location at different times, the federation of the data is not instantaneous.

You can see this by following someone on buzz and immediately reloading the page. It will display that you are not following that person (most the time). Google's infrastructure is better equiped to handle massive scales of data over periods of time using maybe a million machines, this is not the best approach for realtime. They need to transition over to something similar to the Wave infrastructure to get Buzz working correctly as clearly there is something wrong.

It's not just tweets, but many actions within Buzz causes the occassional gap in display.