jerakeen.org

by Tom Insam

notes☴

code☷

links☲

photos☵

photosets.getPhotos comment count

photosets.getPhotos comment count

created 23 September 2009 in links tagged api, flickr and scaling.

Paul speaks Truth.

..while adding more “extras” would reduce the number of API calls needed for a specific application, it doesn’t reduce the load on flickr’s back end systems. We’ve found it actually increases the load, as developers are more likely to request extra data they don’t need, and one heavy API request ties up more of our system resources than multiple lighter API requests.

Also, developer time. But that’s more obvious. What I like is the point that, yes, it’s annoying making n+1 calls, but putting that into one call is still going to end up as n+1 database calls at some point. Joins are Bad. Keep them explicit.

http://tech.groups.yahoo.com/group/yws-flickr/message/5293

Term Extraction and Contextual Web Search services to be discontinued

Term Extraction and Contextual Web Search services to be discontinued

created 11 August 2009 in links tagged api, closure and yahoo.

noooo, I use the term extraction service. Bugger.

http://tech.groups.yahoo.com/group/yws-search-general/mes...

Twitter

New twitter: For the last few days, the delicious API has intermittently returned nothing except an XML comment block. Somewhat annoying.

created 09 March 2009 in stream tagged api and few days.

New twitter: For the last few days, the delicious API has intermittently returned nothing except an XML comment block. Somewhat annoying.

http://twitter.com/jerakeen/statuses/1299634708

Twitter

New twitter: @friedcell I'd advise against it. The Dopplr API (http://dopplr.pbwiki.com/) has a city_search function that will be less fragile.

created 17 February 2009 in stream tagged api, city search and search function.

New twitter: @friedcell I'd advise against it. The Dopplr API (http://dopplr.pbwiki.com/) has a city_search function that will be less fragile.

http://twitter.com/jerakeen/statuses/1218890308

A Warning About the Real Cost of Microformats

A Warning About the Real Cost of Microformats

created 06 February 2009 in links tagged api, compatibility, development, html and microformats.

Would you create a real developer API without a TOS, agreement, or at the very least, guidelines? Are you prepared to deal with objections if, when cutting costs, you rev a frontend design and lose some important aspect of microformat structure on the page (or, god forbid, you just don’t bring microformats over at all). Alternatively, are you prepared to announce all frontend markup changes? Does publishing a microformat without a special agreement mean that you are implicitly allowing comprehensive scraping of your web data?

http://getluky.net/2009/01/08/a-warning-about-the-real-co...

Twitter

New twitter: @simonw Proper API JSON is dense and unreadable anyway. I suggest a 'prettyjson' response type that is served as html and pretty-printed.

created 04 February 2009 in stream tagged api, json and response type.

New twitter: @simonw Proper API JSON is dense and unreadable anyway. I suggest a 'prettyjson' response type that is served as html and pretty-printed.

http://twitter.com/jerakeen/statuses/1176611329

Pinder

Pinder

created 09 January 2009 in links tagged api, campfire and python.

A python api to campfire. I need something like this, but tied into twisted, so that people saying things in channel cause events. It’s not entirely clear if you can get at what people are saying here, other than just polling the transcript list..

http://dev.oluyede.org/pinder/

Google Bookmarks API Guide

Google Bookmarks API Guide

created 10 December 2008 in links tagged api, bookmarks and google.

Google bookmarks doesn’t really have an API. Which is annoying. It doesn’t even seem to obey any of the many many Google authentication systems, so to use it I have to screen-scrape the login dialog.

However, it will serve all the bookmarks as a mozilla bookmarks html file, so I can write a script that pulls the bookmarks down to the local machine and puts them somewhere predicable, so I can use Launchbar to access them quickly. And I get a backup.

All in all, it’s not a bad solution to the ‘I want to put my bookmarks in the cloud’ problem I’ve been trying to solve recently.

http://lnkr.mobi/lnkr/google_bookmarks_api/

Google Reader API

Google Reader API

created 10 December 2008 in links tagged api, google, reader and rss.

unofficial api access to Google Reader data. Not that I have a use for it, but it’s nice to see it

http://www.niallkennedy.com/blog/2005/12/google-reader-ap...

Yahoo! Term Extraction API

Yahoo! Term Extraction API

created 22 September 2008 in links tagged api, keywords, termextraction and yahoo.

Extract keywords from arbitrary text strings. Very easy to use, returns JSON, and seems like it returns pretty good data, too. I’m using this to extract likely-looking tags from my twitters/jaikus on the jerakeen.org lifestream page.

http://developer.yahoo.com/search/content/V1/termExtracti...

Last.fm – The Social Music Revolution

Last.fm – The Social Music Revolution

created 12 August 2008 in links tagged api and lastfm.

The last.fm API. Can’t tell if this is new - I know there was audioscrobbler stuff on the old site, but I think this is more recent. Useful, anyway.

http://www.last.fm/api

Tinder - a Ruby Campfire API

Tinder - a Ruby Campfire API

created 22 March 2008 in links tagged api, campfire and ruby.

I wouldn’t call it great. But it works and is better than anything else out there for talking to Campfire from Ruby. If you want to be able to read what is said in the channel, it’s the only thing.

http://opensoul.org/2006/12/8/tinder-campfire-api

Shelf and the Google Social API

created 04 February 2008 in blog tagged api, google, shelf and social.

The current trunk version of Shelf uses the Google Social Graph API to figure out who owns the web page you’re looking at. If it can’t find a person in the local address book who owns the URL, Shelf can now ask Google if there are any other pages on the internet that link to that page with a rel=”me” relation, and look for those pages in the local address book. So for instance, if I visit my linkedin profile page, Shelf will display context about me, as linkedin links to http://jerakeen.org/. Likewise, any page that I link to from jerakeen.org will be considered mine as well. This elevates Shelf’s context-finding ability to practically magical levels in some cases.

Alas, there are disadvantages. Most superficially, the context-deriving part of Shelf was never designed to make long-running network queries, and so lives in the GUI code. Calling the Google API blocks the GUI thread. This sucks. Fixable, of course, but it makes the current development version somewhat choppy.

More serious is that Shelf now sends the URL of every web page I visit, and the homepages of everyone who’s twitters I read, and the base URLs of every RSS feed I read, to Google. I want to look for context in the email signatures of people that send me mail too, so soon it’ll be sending the homepages of everyone who mails me as well. Some people would consider this creepy. Actually most people would consider it creepy. And I don’t blame them. I don’t really have a solution for this one either, other than a big clearly-labeled option to turn it on.

On the API

For this sort of use the Social Graph API is great. Although all this information is available through just fetching the source of the current page and looking for links myself, there’s no way I’d want Shelf as a local GUI app to be doing that sort of thing. Google aren’t exposing anything I couldn’t have found out myself, but they’re doing it in a simple and fast manner, and using the API is trivially easy. No API keys, dealing with XML, registering my app or anything. I love that they just went with JSON as the format, and hang everything else.

Where’s the next release?

On a related note, Shelf development has been a little slow recently. Partially I’ve been distracted by shipping important features for Dopplr, but mostly it’s because I’ve hit a sort of psychic barrier of progression. Shelf needs a decent caching layer. And a threaded context discovery layer. And a much better event-driven model for display stuff, so it makes a more controlled number of network requests to fetch RSS feeds. Basically, now I’ve explored the problem, I want to rewrite the whole thing to take advantage of my understanding. And that’s boring. So I’m not doing anything. I’ll get over it.

Facebook locks down the feed even more

created 18 January 2008 in blog tagged api, facebook and feed.

Well, as of next month, Facebook developers can no longer put things in a feed unless it’s going in as a direct result of an action that the owner of that feed performed on a facebook page.

Now, this is clearly spun as trying to prevent ‘you’ve been given a beer’ / ‘you’ve been bitten by a zombie’, etc messages. Not letting apps belonging to another person put entries into my feed is a good thing. But the documentation page says

Note that you should not be using a session_key for a user who is not actively using your application when calling this method.

Now, I read this as, you now can’t use a background process to put entries into a user’s feed using a session_id. You can only put things into their feed if they’re looking at your app while you’re doing it. And this is irritating. It completely breaks all the apps I use that syndicate the outside world into my Facebook profile - Twitter, delicious, CPAN, Dopplr, etc.

It seems that this is an effort to stop users like me, who just want to use existing services, but centralize update notification for the friends I have that don’t want to obsessively subscribe to 20 RSS feeds. Naturally, facebook don’t like me, because I don’t see, and therefore click, their ads. Forcing me to visit the site to tell my friends anything ‘fixes’ this.

Maybe I’m paranoid. Maybe I’m mis-reading ‘actively’, and they’re ok with installed apps using session_ids of users who aren’t logged in and using that app at this precise moment. I hope so.

Facebook Developers | Facebook Developers News

Facebook Developers | Facebook Developers News

created 14 December 2007 in links tagged api, change, facebook and platform.

you know, to most people, a 2-week deprecation cycle just before christmas in a platform API that’s implemented by third parties would be considered ever so slightly on the short side. (later - changed to be ~1 month. better)

http://developers.facebook.com/news.php?blog=1&story=61

Automattic Acquires Gravatar « Gravatar Blog

Automattic Acquires Gravatar « Gravatar Blog

created 18 October 2007 in links tagged api, bought and gravatar.

Gravatar bought by the wordpress lot. Large-size icons, and possibly an interesting API.

http://blog.gravatar.com/2007/10/18/automattic-gravatar/

notes on api authentication (tecznotes)

notes on api authentication (tecznotes)

created 15 June 2007 in links tagged api, authentication and secure.

good summary of various ways of doing api authentication

http://mike.teczno.com/notes/api-authentication.html

gotAPI.com :: documentation search engine

gotAPI.com :: documentation search engine

created 13 June 2007 in links tagged api and search.

ajaxy searching across many apis. scary.

http://start.gotapi.com/

WebThumb

WebThumb

created 29 May 2007 in links tagged api, service and thumbnail.

via willison’s oxfordgeeks, an api-based webpage thumbnailer that’s not awful. Maybe now I can stop running my own

http://bluga.net/webthumb/

Backpack Calendar API

Backpack Calendar API

created 24 March 2007 in links tagged api, backpack and calendar.

XML api for the backpack calendar. Very rails-y

http://backpackit.com/api/calendar/

Development « Akismet

Development « Akismet

created 08 November 2006 in links tagged akismet, api, filter and spam.

The Akismet API. shouldn’t be too hard to talk to it from Zimki, and I know the blog apps really need a spam filter.

http://akismet.com/development/api/

Kusor.com: Blogger API - working on Textpattern

Kusor.com: Blogger API - working on Textpattern

created 22 October 2006 in links tagged api, metaweblog and xmlrpc.

A reasonable summary / reference for bits of the metaweblog + blogger + movabletype API. Boy, is this all a huge nasty mess, or what?

http://txp.kusor.com/rpc-api/blogger-api

Plaxo Synchronization API

Plaxo Synchronization API

created 19 September 2006 in links tagged api, plaxo and rest.

The Plaxo REST API. Not that I have an actual use case for this, but I’ll come up with something..

http://www.plaxo.com/api/sync/

del.icio.us: security (everybody feels better with)

del.icio.us: security (everybody feels better with)

created 10 August 2006 in links tagged api and delicious.

It’s a new API. It appears to be mostly compatible, but links posted with the old API now appear to be coming up as broken? This is for mattb, who is adding lots of broken links.. :-)

http://blog.del.icio.us/blog/2006/08/security_everyb.html