Adam Jarret


GTweet Beta 2 Released!

| Tags: google-app-engine, google-reader, gtweet, projects, python, twitter, web-dev

I'm thrilled to announce that GTweet Beta 2 (now with 100% more Python) went live this morning.

For those just joining us, I came back from vacation last week to find the PHP version of GTweet in shambles after my (shared) server collapsed under the pressure, so I decided to port it to Python and move it to Google App Engine.

Please note that this is still very much a beta so please keep those comments and bug reports coming. Related: The only other thing I have written in Python was called Hello World, so be gentle.

Known Issues

  1. I'm not sure why, but sometimes submitting the sign-up form fails. Resubmitting the form seems to work, so if at first you don't suceed...

  2. So far this hasn't been a problem, but I'm worried about those pesky text-encoding bugs rearing their ugly heads, so everyone keep a lookout!

  3. The link to favorite a tweet from within Google Reader is currently missing, but this should return with the next update.

Unfortuantely, all current users must re-make and re-subscribe to their GTweet URLs. Fans should know that I tried two separate approaches to providing backwards compatibility, but I couldn't get it working without relaxing the security of your account information to an uncomfortable degree.

I had been planning new features for GTweet before the collapse, so it was somewhat frustrating to have to re-write existing features in Python, but it ended up being kind of fun.

Python wasn't particularly hard to grasp, but it has it's quirks like any language - a marked lack of curly braces and strict-ish indentation rules made for an interesting Saturday.

GTweet Beta 2 has the same functionality as before with a few differences in implementation:

  1. Your Twitter information is now encrypted and stored in GTweet's Google App Engine datastore instead of being contained in the URL. This change was in the works since before the Python version was needed because it opens the door for some features coming down the road and now seemed as good a time as any to make the switch.

  2. 200 tweets are now pulled every refresh instead of 20 as suggested by Andrew's Comment.

  3. The Reply link should now properly thread conversations in Twitter. Most people won't notice this change, but it's part of being a good Twitter citizen.

  4. Because it's now running on Google's servers, interested folks should check out the link to Google's privacy policy at the bottom of the updated GTweet privacy policy on

Thanks for using GTweet and, as always, let me know what you think in the comments!



The Future of GTweet

| Tags: google-app-engine, google-reader, gtweet, php, projects, python, twitter, web-dev

After a wonderful and relaxing trip to Greece, I returned to a flurry of e-mails warning me that GTweet is down.

Frustrating though it may be, I have the bittersweet problem of having grown too big for my hardware.

As this is currently a hobby project, I don't have the resources to beef up the GTweet infrastructure (read: I'm broke) so I'm thinking about porting the whole thing to Python and running it on the Google App Engine.

As ever the duties of my day job must come first, but I hope to get cracking on a somewhat more scalable version this weekend.

Thanks to everyone who sent in bug reports and other feedback - I find it immensely gratifying that so many people find GTweet useful.

On that note, I know times are tight all over, but if anyone who loves GTweet has a few extra bucks (or pounds, euros, yen or anything else), please consider the Donate button on my projects page. Thanks.

Now, off to learn Python...



Remove Firefox Location Bar Select-All Annoyance

| Tags: firefox, fyi

I just discovered how to change a default Firefox setting that has been bothering me for ages.

The Problem

In Safari (the browser I use most often) single-clicking on the location bar does what most text input fields do: it places the cursor at the location in the text over which you positioned the mouse.

In Firefox, single-clicking the location bar highlights the URL. Without fail, I start typing an addition to the the existing URL only to find that I have erased the text I was hoping to start with.

Whether or not I should just suck it up and learn to touch-type and/or not be so lazy that I don't want to type out an entire URL is beside the point. It's just annoying.

The Solution

Thankfully, it's actually a relatively easy and small change.

  1. Open Firefox and type about:config into the location bar.

  2. Search for the browser.urlbar.clickSelectsAll setting and change it to false by double-clicking it.

  3. That's it! The change should take place immediately without even having to restart Firefox.



Coda Updates to 1.6.3

| Tags: coda, web-dev

As a belated St. Patrick's day gift to us all, Panic released Coda 1.6.3 today.

I haven't had any problems (or noticed anything super-cool) yet, but one point in the release notes caught my attention.

Can now navigate local books while off-line

I wrote about this when I first started using Coda back in November of last year because it seems like a no-brainer.

I tested the new feature and it works as advertised - if you add a book using a file:// url, the "you are not connected to the internet" warning is not displayed when you're offline.

Unfortunately, the warning does not seem to be automatically dismissed for locally hosted books.

For reasons explained in this post, I like to have local copies of books that are served by Apache on http://localhost. It seems as though viewing these books while offline still produces a warning.

Ah well. It looks like I'll be hitting CMD+R when trying to view local books without an internet connection for the foreseeable future. I can't really say I'm too upset, because in reality the times when I'm programming without an internet connection are few and far between.


GTweet: Bugfixes and Beyond

| Tags: google-reader, gtweet, php, projects, twitter, web-dev

I've been attempting to shake any bugs out of GTweet since it's beta release.

One glitch revealed itself when GTweet attempted to display certain html special characters. I applied a fix today, so hopefully we have seen the last of that.

I also increased the text size of the tweet itself and made the tweeter's name a link to that person's Twitter page.

If you use GTweet and have had any technical problems or would like to offer feedback, please contact me at adam at adamjarret dot com.

Thinking about the future, I'm thinking about setting up a forum or wiki for support questions, bug reports and possibly some documentation or an FAQ.

Do any current users have a preference? Are you mailing list people? Let me know in the comments.



GTweet gets official

| Tags: google-reader, gtweet, php, projects, twitter, web-dev pretty much says it all, but as a quick recap for those who don't know: I wrote a PHP application to allow people to read their Twitter feed in Google Reader.

It's currently in beta (and in need of a few good beta testers) but should be feature complete and reasonably reliable. Some of those features include the handling of Twitter authentication, displaying the tweeter's avatar in the RSS feed and the ability to reply to tweets or to favorite them from within Google Reader.

To be clear, favoriting or replying to a tweet opens a new browser window, but the links are provided below the text of each tweet for your convenience.

The service is completely free so why not give it a try? Visit to get started.