How To Enable Extensions For Safari 5

If you, like me, have tried to install a Safari 5 extension such as Coda Notes, and were met with the following dialog:

and then spent 5 minutes looking through Safari’s Preferences window to no avail, this is how you enable Extensions on Safari 5:

  1. Open Preferences
  2. Click Advanced
  3. Click Show develop in menu bar
  4. Close and reopen Safari
  5. Click the Develop menu item
  6. Finally, click Enable Extensions

Viola.

Adam Lisagor: iPad TV

The Sandwich has some thoughts on the iPad, TV, and the rumored new Apple TV. I like what he’s thinking:

Could it be that Apple has chosen to separate our video content and store it temporarily in this ghetto because there is something new and awesome on the horizon? Here’s what I think: Soon enough, that placeholder app called Videos will go away, to replaced by a new app called Apple TV.

The current iPad videos app is a real turd in the iPad’s otherwise beautiful punchbowl. This makes a lot of sense.

Wikipedia Is Broken In Dictionary.app

I’m not sure if this is due to Wikipedia’s new skin (with the “usability” enhancements), some other MediaWiki update, or if the problem is on Apple’s end (Update: It is a problem with Wikipedia’s new skin), but this is another good example of why Apple doesn’t want to rely on third-party vendors for anything.

The image above is what I get when looking up the word “Dictionary” in Snow Leopard’s built-in Dictionary application, and clicking Wikipedia. The Wikipedia page is very long, and should have vertical scrollbars, but there are none.

Update: Mac OS X Hints has information on how a “fix” which involves logging in to Wikipedia and setting your skin to use the previous one.

Hat tip to Shawn Medero.

For The Uninitiated: Web Video Fracas 2010

Adobe wants people to use Flash to play videos, primarily because they own the technology behind it (which makes them lots of money), and have enjoyed the majority of video on the web being played via Flash for quite some time. Adobe, by virtue of owning Flash, is the only real player in the Flash playing and video encoding game. They want Flash on every device in the world, so they can sell their tools to author Flash. Adobe as a company still makes most of their money on selling people tools to make things with. Adobe has spent a lot of money making Flash and their Flash editing tools.

Apple wants people to use H.264 to play videos, primarily because their mobile devices (which make them a ton of money) can decode the video stream in hardware which is a big win in battery life .vs. decoding in software like Flash. Apple controls the decoding of H.264 on the Mac and iPhone/iPad lines, so they don’t have to wait for anyone else when they want to do something new with it. Apple has spent a lot of money and time making H.264 work great on their devices.

Google just wants people to play videos. They’d prefer it if the technology used to encode and playback those videos didn’t belong to anyone, so they don’t have to deal with the politics of being nice to some other company because they need their support vis-a-vis video. They bought a company called On2 and open sourced a video codec and container format (which may have some severe patent problems) to accomplish this end and try to diffuse the situation. Google is the only company in this tug-o-war who actually makes money selling videos, or more precisely, renting the eyeballs of people who are viewing videos to advertisers.

Due to the above, video on the web is a nightmare right now. There is no video format you can encode to that will play in the big three: Safari, Firefox, Internet Explorer, unless you want to use Flash to play the video. Which means users will need to have Flash installed on their device, in which case it will not play on the largest mobile device market: the iPhone, iPod Touch, and iPad, or even current releases of the smaller ones, like Android, which also do not support Flash. If you encode to H.264, it won’t play in Firefox or the current version of Internet Explorer (8), but will work in Safari, Chrome (on the Mac), and the upcoming version of Internet Explorer (9). Adobe has pledged to support WebM in it’s Flash products.

There is no way Apple is going to support WebM for their mobile platform unless it can be decoded in hardware. Broadcomm, a major producer of chips for mobile device, has announced a chip which will decode VP8 in hardware, but this is fairly new development. It is not unreasonable to consider that Apple has plenty of so-called “skunkworks” projects to play all kinds of Video content on iPhone and iPad, but it’s pretty unlikely that we’ll see any new video support in the upcoming new iPhone model.

The App Store: Revenge Reviews

Garret Murray, developer of the Ego app for iPhone, on what he calls “revenge reviews”: Reviews posted to the App Store by users who accidentally purchased an app, misread it’s description, or otherwise made a mistake. I hadn’t thought of this:

People brought up a great point the last time I complained about App Store customers—they’re all children. Not metaphorically, but literally. Most of these customers are kids with iPod Touches. So of course they act like children.

But it rings true. I’d go further and say that the ones that are not literally children, are probably emotionally stunted in some way.

Apple’s Use Of Private APIs In The App Store, iTunes Music Store

John Gruber notes, vis-a-vis this talk given by Bertrand Serlet on Apple’s API Lifecycle, that:

Apple doesn’t disallow the use of private APIs out of spite; they disallow it because their private APIs are not fully baked.

It should be obvious, but: Apple’s intentions are utterly unimportant in this matter. Using private APIs for system-level applications is one thing, but iBooks is in the App Store. iBooks uses private, Apple-only APIs that are not available to other developers. iBooks directly competes with any number of other applications that sells things to read. iBooks is using an unfair advantage given to it by Apple’s engineers. There’s nothing ok about any of that.

Adding to this, there is the potentially coming storm of a United States .vs. Microsoft situation regarding the iTunes Music Store. There are other music stores out there, after all, and Apple has not put them all on equal footing. If using special features that no other developers have access to isn’t an anti-competitive practice, I’m not sure what else qualifies.

The more iPads, iPhones and Macs that Apple sells, the closer they’re coming to an antitrust showdown.