owencm
Joined 14 years ago
Karma
226
Submissions
48
Member since
Apr 26
CS Undergrad, Oxford. APM intern, Google.
View on Hacker NewsRecent submissions
Comment · 10 years ago
Co-author of the article here.
I agree with dpark - an unstated goal of this proposal was for developers to be able to easily move legacy sites with legacy endpoints to long sessions without needing to update those endpoints or pages.
The service worker approach can effectively intercept requests to any endpoint and perform the re-generation of a short cookie if needed, without needing to change every page on the site or the legacy endpoints.
Comment · 10 years ago
Co-author of the article here.
An unstated goal (we probably should have stated it, looking back) was for sites to be able to easily move legacy sites with legacy endpoints to long sessions.
The service worker approach can effectively intercept requests to any endpoint and perform the re-generation of a short cookie if needed, without needing to change every page on the site or the legacy endpoints.
One additional benefit is that it minimizes the transmission of the long term token, which is generally good if you're worried about it somehow getting intercepted. You may or may not be too concerned about that risk though.
Comment · 10 years ago
(Disclaimer: I work on these features on Chrome)
We're exploring that. It's not 100% clear either way, but I personally hope we can do it.
Feel free to star this issue if you want to keep track of progress: https://bugs.chromium.org/p/chromium/issues/detail?id=516147
Comment · 10 years ago
Mods - title should read "Native Mac Notifications Behind A Flag in Chrome Stable"
Comment · 10 years ago
Comment · 10 years ago
Looks great! Out of interest, does this take advantage of any native features via node or could it also be a website?
I'm curious if the motivation of making a desktop app was just for the "installed app user experience" or because it was needed to access some API.
Comment · 11 years ago
FWIW Alex Russell wrote a great article about why our current approaches don't work and why this is interesting to explore: https://infrequently.org/2015/08/doing-science-on-the-web/
[Full disclosure: I work on this project]
Comment · 11 years ago
But it's opt out vs opt in which is a huge difference.
Comment · 11 years ago
Sites can definitely work offline using the new Service Worker system: http://www.html5rocks.com/en/tutorials/service-worker/introd.... Try this example: https://voice-memos.appspot.com.
Comment · 11 years ago
That feature was designed but never built, so his point still stands. In my ideal world sites can do that stuff, they just have to ask, and users can always say no.
Comment · 11 years ago
Actually, sites in Chrome can work fully offline today using Service Worker (http://www.html5rocks.com/en/tutorials/service-worker/introd...). And they can get users to add the site to their homescreen, so they have the full icon+offline experience (https://developers.google.com/web/updates/2015/03/increasing...).