====== It's everywhere! ======
LOLCODE is cropping up everywhere I look. It's becoming unsettling. First, I learned of [[http://pownce.com/leahculver/notes/2009030/|Leah Culver's]] work on the [[http://pownce.com/api/|Pownce API]]. LOLCODE is a legitimate return format: just append ''.lol'' to your request:

[[http://api.pownce.com/users/atl.lol]]:\\
<code>OH HAI
INVISIBLE FLICKR API OM NOM NOM NOM
  GIMME USER
    I CAN HAS USERNAME
      atl
    KTHX.
    I CAN HAS FRIEND_COUNT
      27
    KTHX.
    I CAN HAS PERMALINK
      http://pownce.com/atl/
    KTHX.
    ...
  I IS BORED
KTHXBYE.</code>

But then I learned it was just in emulation of the [[http://www.flickr.com/services/api/|Flickr API]] (as implied by the second line of the response), where, thanks to [[http://www.iamcal.com/|Cal Henderson]], ''format=lolcode'' sits proudly next to ''xmlrpc'' and ''json''.

[[http://api.flickr.com/services/feeds/photos_faves.gne?nsid=98805480@N00&lang=en-us&format=lolcode| http://api.flickr.com/services/...&format=lolcode]]:
<code>HAI
IM IN UR BUCKETS MAKING UP FORMATS
GIMME A_T_LS FAVORITES
  I CAN HAS PHOTO 2008_04_25_ROFLCON_10
    ITZ AT http://www.flickr.com/photos/docsearls/2442343070/
    INVISIBLE METADATA
    LOL
  KTHX.
  I CAN HAS PHOTO ICANHASCASESTUDY
    ITZ AT http://www.flickr.com/photos/stoast/2444666738/
    INVISIBLE METADATA
    LOL
  KTHX.
  I CAN HAS PHOTO ICANHASCASESTUDY2
    ITZ AT http://www.flickr.com/photos/stoast/2443843469/
    INVISIBLE METADATA
    LOL
  KTHX.
...</code>

Really, you have to admit that as API formats go, this is pretty easy to read. I look forward to seeing it elsewhere: if you spot it, as always, you can send a note to <lolcode@lolcode.com>.