Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on May 26, 2014
  1. Update app name, version, API keys with -hrd suffix

    I tried updating to a new Google Maps API key as specified in the below link, but that just seemed to break it. This one API key seems to work for multiple domains now, so I'm just not going to mess with it for now.
  2. Reset Bitly API key

Commits on Feb 7, 2014
  1. Bump app version, don't update Google Maps to APIv3

    The email they sent is as follows, but it seems like the wrapper is working fine:
    Dear Google Maps API Developer,
    We are contacting you because your email is associated with the Google Maps JavaScript API v2 key being used for the following domains:
    As you may be aware, JavaScript Maps API v2 was scheduled for shutdown on May 19, 2013. After listening to feedback from developers we decided to [extend the deprecation timeline]( by six months, to November 19, 2013 to allow more time for migration to v3 of the API.
    On November 19, 2013 we will deploy a JavaScript wrapper that attempts to automagically turn remaining v2 maps into v3 maps. Though we expect this wrapper to work for most simple maps, we cannot guarantee that your maps will continue to function. We therefore highly recommend that you migrate to v3 before November 19. The good news is that Google Maps JavaScript API v3 is more robust and feature rich than v2, and we’ve written a [guide to assist the migration](
    Google Maps API Developer Relations
    You have received this email service announcement to update you about important changes to the Google Maps API sites that are related to your email address.
    If you would like to stop receiving updates, please let us know by filling in this form.
    © 2013 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
  2. Fix offset map on logged-out home page

    Not sure why it got offset? But oh well...
  3. Minor tweak to support more recent 4sq API version

    An email from them said "While we have your attention, you should be aware that we also plan on dropping support for API requests before 20120609. This change will happen in early 2014, and we will confirm the exact date in a future announcement."
  4. Specify version date for Foursquare API

    As required as of 20140128 and as specified in
Commits on Jan 17, 2012
  1. Fixed broken default map, and a bug where map tiles near the Internat…

    …ional Date Line were getting requested with a Longitude of -182.109375 by Google, which was causing my geomodel provider to fail.
  2. Group the overlay clearing with the creation, so you don't get cases …

    …where there are two identical overlays making everything really dsaturated.
  3. Doh, fixing that error from commit before last in the uservenue creat…

    …ion for real. It was failing, I think, if a venue didn't have a latitude and longitude, rather than just skipping the venue.
  4. Was seeing an error in the logs where this wasn't defined, and it was…

    … failing on the append call, so this should fix it.
Commits on Jan 15, 2012
  1. Make the links at the bottom open in new tabs, in case the user gets …

    …bored while tiles are loading.
  2. Fixed UI for when the user's check-in's have been cleared. Various ot…

    …her small changes to the copy and javascript. Possibly done?
Commits on Jan 14, 2012
  1. Fixed static map generation to properly show progress to the user and…

    … keep track of when it was finished.
  2. removing unused stuff

  3. Added setTimeout and clearTimeout to javascript so that it waits befo…

    …re fetching new tiles, which should ease load on server a bit during the customizing process.
  4. Reset venue counts to 0, not -1. Fixed several tile rendering edge ca…

    …ses, including one in which it seems to have been maxing out on the number of venues in a tile at 1000.
  5. Fixed is_ready issue (I think) by removing update_user_info call from…

    … the IndexHander - it's likely that it was undoing the is_ready=True by putting an old copy of the UserInfo back in the datastore. Re-fixed static map generation, since I was accidentally truncating my latlng floats and somehow lost that change before. Split task queues into two, based on type of work.
Commits on Jan 13, 2012
  1. Accidentally undid an earlier fix for tile drawing. Had an idea to fi…

    …x is_ready, and it seems like a Good Idea, but it didn't fix it...
  2. Lots of improvements, forgot to commit earlier. I had a lot of troubl…

    …e with the UserInfo is_ready flag used by the frontend to know when the backend has all of a user's check-ins. It was getting set properly to True in the fetch_and_store_checkins_next function when it got to the end of the history, but then when it was queried by the handler for is_ready, it was still False. I couldn't figure out why, but I was able to work around it by making sure the initial fetch_and_store_checkins_next did not fetch *all* of the user's check-ins. It now starts off with only 2 :-/
Commits on Jan 8, 2012
  1. Static tile images unfinished, pausing to figure out how I broke tile…

    … generation to only display from upper right.
  2. Lots of fixes. Finished cleaning up venue code now that it doesn't ne…

    …ed to worry about legacy UserVenue data and background checking. Fixed bug around fetching new data and deleting data. Tile generation is now more efficient, but not efficient enough to generate my static map of NYC.
Commits on Jan 3, 2012
  1. Assorted fixes to template displaying so that the login and logout bu…

    …ttons show up correctly. A few handler changes. Still trying to delete all the UserVenues, ugh.
  2. No longer permanently storing venues for users, since that DB was gro…

    …wing unmanageably large. Wrote script to clean out old UserVenues a week after the last activity. This is good anyway, since I don't reaaaally want to be storing that much userdata forever. TODO: change UserInfo back to db.model
Commits on Jan 2, 2012
  1. Merge pull request #2 from tganzarolli/master

    Porting to Foursquare v2 API (at last!)
Something went wrong with that request. Please try again.