{"action":"created","issue":{"url":"https://api.github.com/repos/google/physical-web/issues/262","repository_url":"https://api.github.com/repos/google/physical-web","labels_url":"https://api.github.com/repos/google/physical-web/issues/262/labels{/name}","comments_url":"https://api.github.com/repos/google/physical-web/issues/262/comments","events_url":"https://api.github.com/repos/google/physical-web/issues/262/events","html_url":"https://github.com/google/physical-web/issues/262","id":54006085,"number":262,"title":"Dynamic metadata","user":{"login":"dermike","id":4582134,"avatar_url":"https://avatars.githubusercontent.com/u/4582134?v=3","gravatar_id":"","url":"https://api.github.com/users/dermike","html_url":"https://github.com/dermike","followers_url":"https://api.github.com/users/dermike/followers","following_url":"https://api.github.com/users/dermike/following{/other_user}","gists_url":"https://api.github.com/users/dermike/gists{/gist_id}","starred_url":"https://api.github.com/users/dermike/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dermike/subscriptions","organizations_url":"https://api.github.com/users/dermike/orgs","repos_url":"https://api.github.com/users/dermike/repos","events_url":"https://api.github.com/users/dermike/events{/privacy}","received_events_url":"https://api.github.com/users/dermike/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/google/physical-web/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2015-01-11T21:38:37Z","updated_at":"2016-09-16T15:50:17Z","closed_at":"2015-09-19T21:35:42Z","body":"I've been thinking a lot about dynamic metadata ever since Physical Web got published. I haven't had time to test anything of it yet, but it seems like a cool idea to be able to have a dynamic metadata description for example the bus stop. The page could generate the description based on time of day: \"Next departures 14.00, 14.20, 14.40...\" etc, so the user won't even have to open the browser to know when the next departure is. \r\n\r\nIs this something that would not work because of the caching, or a bad idea in general considering the goals of the project?"},"comment":{"url":"https://api.github.com/repos/google/physical-web/issues/comments/247636352","html_url":"https://github.com/google/physical-web/issues/262#issuecomment-247636352","issue_url":"https://api.github.com/repos/google/physical-web/issues/262","id":247636352,"user":{"login":"scottjenson","id":1055674,"avatar_url":"https://avatars.githubusercontent.com/u/1055674?v=3","gravatar_id":"","url":"https://api.github.com/users/scottjenson","html_url":"https://github.com/scottjenson","followers_url":"https://api.github.com/users/scottjenson/followers","following_url":"https://api.github.com/users/scottjenson/following{/other_user}","gists_url":"https://api.github.com/users/scottjenson/gists{/gist_id}","starred_url":"https://api.github.com/users/scottjenson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scottjenson/subscriptions","organizations_url":"https://api.github.com/users/scottjenson/orgs","repos_url":"https://api.github.com/users/scottjenson/repos","events_url":"https://api.github.com/users/scottjenson/events{/privacy}","received_events_url":"https://api.github.com/users/scottjenson/received_events","type":"User","site_admin":false},"created_at":"2016-09-16T15:50:17Z","updated_at":"2016-09-16T15:50:17Z","body":"At this point the cache is updated every 5 minutes. There are no controls but we're considering support http-cache headers to let it be *longer*. We're a bit worried the making it shorter will increase the overhead of our server. "}}
{"actor":{"display_login":"scottjenson"}}