{"action":"closed","issue":{"url":"https://api.github.com/repos/mozilla-services/pageshot/issues/164","labels_url":"https://api.github.com/repos/mozilla-services/pageshot/issues/164/labels{/name}","comments_url":"https://api.github.com/repos/mozilla-services/pageshot/issues/164/comments","events_url":"https://api.github.com/repos/mozilla-services/pageshot/issues/164/events","html_url":"https://github.com/mozilla-services/pageshot/issues/164","id":58381689,"number":164,"title":"Create stable shot URLs","user":{"login":"ianb","id":44390,"avatar_url":"https://avatars.githubusercontent.com/u/44390?v=3","gravatar_id":"","url":"https://api.github.com/users/ianb","html_url":"https://github.com/ianb","followers_url":"https://api.github.com/users/ianb/followers","following_url":"https://api.github.com/users/ianb/following{/other_user}","gists_url":"https://api.github.com/users/ianb/gists{/gist_id}","starred_url":"https://api.github.com/users/ianb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ianb/subscriptions","organizations_url":"https://api.github.com/users/ianb/orgs","repos_url":"https://api.github.com/users/ianb/repos","events_url":"https://api.github.com/users/ianb/events{/privacy}","received_events_url":"https://api.github.com/users/ianb/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mozilla-services/pageshot/labels/needs%20discussion","name":"needs discussion","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-02-20T17:09:54Z","updated_at":"2015-03-24T21:36:01Z","closed_at":"2015-03-24T21:36:01Z","body":"I think shot URLs should be associated with the original URL.  This fits a future model where we have one shot per person per URL.  (A shot can still have different facets or versions.)\r\n\r\nWe will want to canonicalize the URLs to make this more stable, though we could start by mostly punting on this.\r\n\r\nWe can use a hash to put this together.  The URLs should not be guessable by a third party.  So we'd take some user private identifier (also known by the server) and the URL and concatenate them and hash.  And probably truncate.\r\n\r\nOne nice thing is we can \"know\" the URL of the shot before the shot is created.  Also it makes it easy to fetch shot data if there is existing shot for this URL.\r\n\r\nI'm worried about this become really confusing for highly dynamic pages, like an app or index page.\r\n\r\nIt's unclear to me if we want to include page fragments in the URL."}}