Typo Flickr Fix
Posted by Scott Laird Fri, 01 Sep 2006 05:32:29 GMT
A number of people have pointed out that Typo’s Flickr API key has expired. The situation is actually slightly more complex, but the fix is dead simple. See changeset 1256 for the fix. If this works for everyone, then I’ll roll 4.0.4 over the weekend.

I applied (and recieved) a flickr key about a week ago for a custom app that I was coding, and now my key is also expired. I tried a new key and it claimed it was expired too.
See like something wierd is happening with flickr keys ….
Yeah something weird is happening: the Flickr devs are acting like idiots. Basically a signature is required on all auth calls now. Something which was supposedly in the docs all the time but until now wasn’t actually required (due to a bug). Thankfully, they’ve fixed that bug now so everyone’s libraries and custom apps based on the API are now broken. Thanks Flickr!
</sarcasm>
That may be the case, but that has NOTHING to do with why Typo broke. We don’t even authenticate with Flickr; we’re just using public data.
We broke because the Ruby Flickr library that we’re using has a hard-coded API key, and it uses it instead of the one that you feed it. That’s the key that expired.
I suspect that this is biting a lot of Ruby apps.
The fix works for me. Thanks.
Speaking of Typo…
“typosphere.org coming soon
We are in the middle of creating a new home page for the Typo project.”
Is Typo going to get a homepage anytime soon (preferably before Windows Vista is released)?
The fix works here as well. Cheers.
FYI, there is a bug in flickr.rb where it tries to use its own API key rather then the one passed in the constructor. And its key expired on Aug 30th.
I just went to look at the change set. The link isn’t working for me.
Speaking of Flickr, is this bug in the MetaWeblogApi implementation fixed:
http://rubyforge.org/pipermail/typo-list/2005-December/001342.html
Tried to look up the bug, but looks like the trac is down.
Would love to be able to post from Flickr and 43 Things. Every other client I use seems to work just fine.
Yes, I was looking into the fix but Trac is temporarily down (for good reason according to typosphere), but this means that I am unable to see the changes.
Is there any way that I can find the changeset? Thanks