To prevent MITM attacks, Service Workers _require_ HTTPS. HTTPS isn't as accessible as unencrypted HTTP and self signed certs trigger user scarring warning messages. I do think HTTPS is better for privacy to an extent, but unless people can get signed certs for cheaper than their domain name, part of me feels like were only allowing additional web functionality for those able to afford SSL certs. Of course, cheap certs makes this argument null and void. Does anyone have any recommendations?
Also, I think it's been shown that the overhead of encryption isn't that expensive these days.
What's completely broken about it? If you use it the way it was intended to be used, as a cache for apps, then it works perfectly fine in my experience. It behaves like a native app that updates itself in the background (Chrome itself does this, for example). If you try to use it as a HTTP cache then yes, it's completely the wrong tool for the job and you're gonna have a bad time.
Comments
AppCache sucks. It's completely broken.
At least we have the Service Workers spec[0] coming soon, though, which should solve the problem.
[0] https://github.com/slightlyoff/ServiceWorker/
To prevent MITM attacks, Service Workers _require_ HTTPS. HTTPS isn't as accessible as unencrypted HTTP and self signed certs trigger user scarring warning messages. I do think HTTPS is better for privacy to an extent, but unless people can get signed certs for cheaper than their domain name, part of me feels like were only allowing additional web functionality for those able to afford SSL certs. Of course, cheap certs makes this argument null and void. Does anyone have any recommendations?
Also, I think it's been shown that the overhead of encryption isn't that expensive these days.
The cheapest certs I've found are from https://www.gogetssl.com/domain-validation/comodo-positive-s... but the wildcards are still pretty expensive. I can't recommend them though as I haven't bought one yet.
You can get cheap wildcard SSL from here - http://bit.ly/cheap-wildcard-ssl-cert.
Heer you can find Comodo PositiveSSL Wildcard at $58.36/Year.
What's completely broken about it? If you use it the way it was intended to be used, as a cache for apps, then it works perfectly fine in my experience. It behaves like a native app that updates itself in the background (Chrome itself does this, for example). If you try to use it as a HTTP cache then yes, it's completely the wrong tool for the job and you're gonna have a bad time.