Tag Archives: chrome

Add Sites to Google Reader with Just One Click

1. Head to Google Reader and click Settings, Reader settings.

2. Click the Goodies tab, then scroll down until you see Subscribe as you surf.

3. Drag the Subscribe… link to your browser's bookmarks/favorites bar.

That’s all there is to it! When you click the bookmarklet (so named because it’s a bookmark that performs a special function, rather than just directing you to a page), you’ll be taken straight to Google Reader. There you’ll see a few key stats about the feed (such as average number of posts per week) and a Subscribe button you click to complete the process.

via Add Sites to Google Reader with Just One Click Bookmarklet – Marklets.com.

Way, way, WAYYYY better than the current dance I’ve been doing:

  1. See if the site I want to subscribe to has a link to it’s RSS feed on the page somewhere.
  2. If it does, click the link that takes me to the RSS page.
  3. Copy the RSS URL.
  4. Switch to Google Reader (I run a separate Fluid instance of Reader as an Single-Site-Browser).
  5. Hit “a” (the keyboard shortcut for adding a subscription).
  6. Paste in the RSS URL.
  7. Hit “enter”.

The process is about 1,000,000 times worse if the site in question doesn’t have an easily-visible RSS link:

  1. Copy the site’s URL.
  2. Open Firefox (Chrome, as far as I can tell, doesn’t allow me to easily access the RSS feed).
  3. Paste in the site’s URL.
  4. Click the RSS icon in the location bar, which takes me to the RSS page.
  5. Copy the RSS URL.
  6. Switch to Google Reader.
  7. Hit “a”.
  8. Paste in the RSS URL.
  9. Hit “enter”.

A couple of additional steps, but you can see how it was an convoluted solution for a simple problem.

I do love bookmarklets.

Google Chrome is AWESOME!

If you don’t know what Google Chrome is, either your feed reader is broken (and you need to recompile it from scratch), or you live under a rock. Those are the options.

I’m hoping that more people will be interested in this than DosBox…

If you’re running Windows as your OS of choice, and haven’t tried out Chrome yet, I urge you to do so at google.com/chrome – hit this link.

Otherwise, if you’re running Linux or OSX as your OS of choice, read on…

I’ve found the Google Chrome – Platform Specific Build Instructions here.

Mac (I didn’t go to the trouble to go and compile it. I have no need.)

Windows (bear in mind that while they do provide binary versions of the Chrome Beta for Windows, there is no reason to stop you from download the source and compiling it yourself.)

Linux (Hardcore *nix fans will no doubt love watching the Chrome source scroll past their screen – you geeks 😛 )

Now, some extra info:

  • Google Chrome is strictly a BETA at this stage. The version number is 0.2, so make of that what you will.
  • Chrome renders webpages with the WebKit rendering engine – along with Safari. By contrast, Firefox uses the Gecko rendering engine.
  • Technically, you’re allowed to ignore the EULA if you compile the source code yourself. (via Ars Technica)
  • It’s fast. Faster than Firefox. Javascript is especially so – Lightboxes are instantaneous.

There is one feature I like particularly; the ability to give sane error messages. Take, for example, the message that you get when you type in a wrong URL into the address bar. Compare the message that you get with Chrome:

…to the one that greets you in Firefox. Which of the two would you be more likely to understand? (Granted, if you’re reading this website you can probably understand them both, but still!)

It’s the little things like that that will make the difference – everyday users are supposed to be able to USE things. Not have a masters in computer science just to operate their webbrowser. Okay, so that last commend was a little harsh – but you get the picture, usability is damned important! Chrome even provides you with a Google search (haha) to help you. I love Google. I love Chrome.

Now, if only they had a Mac version – from my initial impressions in a Windows VM, I’d easily use it over Firefox.