4 ms·
I am not up to date on this kind of technology, but reading the article, this sound terrible! Not the guardians implementation, but the concept of locally "cach
by Grumbledour 6y ago
I am not up to date on this kind of technology, but reading the article, this sound terrible! Not the guardians implementation, but the concept of locally "caching", though I would call it installing, executable code, that can then intercept network requests and basically do whatever it wants? Why would we think this is a good idea?
I am not surprised by Chrome doing something like this. But firefox too? I hope this will be opt-in.
- Narretz 6y agoService workers have been around for a while. As far as I know their capabilities are restricted to the domain that includes them. So the guardian website can only intercept network requests made from itself.
- Grumbledour 6y agoWell, just goes to show you how out of date I am! Though after reading up on it, I still don't like it much. It makes the web behave in ways I don't expect it to and I don't really see why anyone would really need this, unless they want to fundamentally change the way the web is expected to work.
- nicoburns 6y agoIt's main usecase is for making web apps work offline. This allows you to "install" a web app rather than a full-blown native app. If iOS supported it properly, then you could have truly cross platform, sandboxed mobile apps. There used to be a declarative version AppCache, but in pracrice that made cache invalidation almost impossible to manage properly.
- rzzzt 6y agoYou can check "about:serviceworkers" on Firefox, and see how many sites install a worker when visiting their page. Spoilers: a whole lot of them
- geofft 6y agoIt can't do whatever it wants. It can make responses for requests that would go to that particular website without actually making the request, that's it - that is, the website can provide some code that makes local responses on its behalf for things it could respond to anyway. It can't intercept (or even see) anything for other sites. That's a significant difference from installing executable code in the form of a standalone binary. I do agree, more broadly, that there's a place in this world for a s web-like thing that only lets sites provide text and minimal formatting and doesn't let them run any code at all, even in a constrained/sandboxed environment. (https://gemini.circumlunar.space/ https://gemini.circumlunar.space/ seems like the most promising thing in this space.) But the web hasn't been that since 1995 when they released LiveScript.
- SyneRyder 6y agoThere's also the original pre-web Gopher protocol, which has been getting a lot more users since being mentioned on HN a few weeks ago together with Gemini. Gopher seems to appeal to people who like retro-computing - the TLS requirement of Gemini rules out even older Macs, nevermind the Apple IIs and Commodore 64s that can still access Gopher. For anyone curious, Phetch is a really good terminal-based browser for Gopher written in Rust [1], and Jaruzel's Gopher Browser For Windows is a very easy to use GUI browser that also supports image files. Both are under 1MB. (If you're running Haiku OS, Gopher is still built-in to the default WebPositive browser.) [1] https://github.com/xvxx/phetch https://github.com/xvxx/phetch [2] http://www.jaruzel.com/gopher/gopher-client-browser-for-windows http://www.jaruzel.com/gopher/gopher-client-browser-for-wind...