Reminder about Chrome Installation

Just a post to remind everyone of the current (annoying) directions on how to install rbutr:

  1. Download the extension file from the website and save it to your computer.
  2. Click the spanner icon on the browser toolbar.
  3. Select Tools > Extensions.
  4. Locate the extension file on your computer and drag the file onto the Extensions page.
  5. Review the list of permissions in the dialogue that appears. If you would like to proceed, click Install.
The original post we made about this can be seen here:

I’m reposting this because the older post is sinking down in to our history, and less obvious to see now, and with more people visiting from Phil Plait’s post of Tim Farley’s TAM2012 talk today, I think it is worth making this information a bit easier to find.

About The Chrome App Store Situation

Just to clarify what has happened here, we have been happily self hosting our beta version of rbutr since March without any problems. We chose to self host because we are still developing, and it just makes it easier to roll out the regular changes we are making. But then about a month or two ago Google Chrome changed their policy on extensions, and with the following Chrome update no self hosted plugins are automatically installed anymore – you have to manually do it according to the instructions above.

So we started working on getting our app ready for the Chrome Store. We actually thought we had it, and started testing the new version which Craig had hacked together and uploaded in to the store, but digging deeper we found that Chrome has also implemented more strict changes in the newer versions of chrome, which, if I recall correctly (Craig is the man to speak to about this stuff), won’t allow us to use Javascript in our extensions popup… or something like that.

Whatever the exact details of it are, the point is that in order to move our app in to the store, we have to implement significant changes to the way the actual extension works. Craig has started working on it, but it is a bigger job than we really wanted to spend time working on (it isn’t like we don’t have plenty of other jobs to be working on!). This is just a reminder to us of one of the complications of needing to work within the frameworks provided by other companies who are all free to change their technology and policies at any time without warning.

On the positive side, it might help bring us closer to a firefox version of rbutr, since Craig is working on the plugin again anyway 😀

Share Button