change url convention in preparation for backbone

In this case we are making a second request to the server to fetch the data through ajax, but ideally the base page would be small and/or cached and provide a loading indicator. This can actually improve user experience for large files.

Backbone routers work much better when there are no changes in the base url and all changes are in the hash

The only possible negative effect here is the reduction of the users' perception of security that came from the separation between the hash and the query. However, mega.co.nz does it this way too and I haven't heard complaints.
add backbone and underscore
robust error handling for invalid paste names
switch to using a backbone router
start to get rid of getParams and pageKey
perserve key cleaning code
fix missed reviison number
reorganize html to organize it into backbone views
make preview its own route
create views
combine preview and read
simpler transitions between pages
fix flash of read-page when the page is loaded
introduce basic templating
make templates use text/template type
use backbone event delegation system
use templating for pastelink
clean up initialization code
more send_data into view
move out upload_paste function