{"action":"created","issue":{"url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/41","labels_url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/41/comments","events_url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/41/events","html_url":"https://github.com/slightlyoff/BackgroundSync/issues/41","id":57327496,"number":41,"title":"Should the ID be auto-generated by default?","user":{"login":"jkarlin","id":6920902,"avatar_url":"https://avatars.githubusercontent.com/u/6920902?v=3","gravatar_id":"","url":"https://api.github.com/users/jkarlin","html_url":"https://github.com/jkarlin","followers_url":"https://api.github.com/users/jkarlin/followers","following_url":"https://api.github.com/users/jkarlin/following{/other_user}","gists_url":"https://api.github.com/users/jkarlin/gists{/gist_id}","starred_url":"https://api.github.com/users/jkarlin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jkarlin/subscriptions","organizations_url":"https://api.github.com/users/jkarlin/orgs","repos_url":"https://api.github.com/users/jkarlin/repos","events_url":"https://api.github.com/users/jkarlin/events{/privacy}","received_events_url":"https://api.github.com/users/jkarlin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-11T15:08:07Z","updated_at":"2015-02-13T08:28:49Z","closed_at":null,"body":"@annevk @clelland @jakearchibald \r\n\r\nAs of ccdb392126ca4e8b41ddfc7685a1f0603ce258b8 the id can be default set by the UA. After some thought, I don't like the idea of a default id.\r\n\r\n1) What are the use cases for a default id? I can only think of calendar events, and we're not (currently) supporting exact timers anyway. And even for a calendar, you could compose an id based on the name and time of the event. This would also help to prevent duplicate registrations.\r\n\r\n2) Default id makes it easy to accidentally double register. Imagine the page registers a repeating sync each time it's opened. If it had to use the same id each time the registration would reject.\r\n"},"comment":{"url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/comments/74220349","html_url":"https://github.com/slightlyoff/BackgroundSync/issues/41#issuecomment-74220349","issue_url":"https://api.github.com/repos/slightlyoff/BackgroundSync/issues/41","id":74220349,"user":{"login":"annevk","id":1544111,"avatar_url":"https://avatars.githubusercontent.com/u/1544111?v=3","gravatar_id":"","url":"https://api.github.com/users/annevk","html_url":"https://github.com/annevk","followers_url":"https://api.github.com/users/annevk/followers","following_url":"https://api.github.com/users/annevk/following{/other_user}","gists_url":"https://api.github.com/users/annevk/gists{/gist_id}","starred_url":"https://api.github.com/users/annevk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/annevk/subscriptions","organizations_url":"https://api.github.com/users/annevk/orgs","repos_url":"https://api.github.com/users/annevk/repos","events_url":"https://api.github.com/users/annevk/events{/privacy}","received_events_url":"https://api.github.com/users/annevk/received_events","type":"User","site_admin":false},"created_at":"2015-02-13T08:28:49Z","updated_at":"2015-02-13T08:28:49Z","body":"@KenjiBaheux ah, I just had the same thought, though I would pick the empty string. However, it's still unclear to me why the one-off wake-when-online use case requires an ID to begin with."}}