<story><title>Firefox Local Files Theft – Not Patched Yet</title><url>https://quitten.github.io/Firefox/</url></story><parent_chain><item><author>majewsky</author><text>Is it really that hard to run `python -m http.server` in your repository?</text></item><item><author>mort96</author><text>Learning web programming is amazing, since you can just start writing a .html file and open it in a browser. There is no need to learn how go set up a local http server. Chrome truly is killing that experience; you can&amp;#x27;t even load javascript modules without http involved now outside of Firefox.&lt;p&gt;I really hope Mozilla doesn&amp;#x27;t &amp;quot;fix&amp;quot; this &amp;quot;vulnerability&amp;quot; by destroying the experience of people learning web programming like Google did.</text></item><item><author>est31</author><text>IMO, the approach taken by Chrome and other browsers is over restrictive, basically killing off the file:&amp;#x2F;&amp;#x2F; protocol. Already now it&amp;#x27;s impossible to load wasm files in the file:&amp;#x2F;&amp;#x2F; protocol in Chrome, and I think this also had implications on using wasm in electon.&lt;p&gt;Ultimately, file:&amp;#x2F;&amp;#x2F; is a great, cloud free method of having web pages and applications and it should stay that way instead of forcing everything to be networked and reliant on third party computers or domain names.&lt;p&gt;There are so many reports, documents, etc that live as non-networked html files. E.g. rust documentation (cargo doc --open) is generated as html files on-disk and then just displayed without the need for a webserver. Starting a localhost webserver is in fact &lt;i&gt;less&lt;/i&gt; secure than file because now every user on the computer has access instead of just the users with read-access to the files. This has thankfully been fixed in Chrome OS though.&lt;p&gt;Responsive web apps are not the solution as they still need &amp;quot;seeding&amp;quot; via the network. Maybe some kind of standardized format where you have a glorified zip file with some metadata and when you double click it, it opens in the web browser which starts a web server in the background that runs a specially designated js in that zip file and which can accept usual fetch requests and has read access to the entire zip file. The browser&amp;#x27;s &amp;quot;UI&amp;quot; would then communicate with the server via well-known protocols.</text></item></parent_chain><comment><author>nemetroid</author><text>I started learning HTML at age eight. No one in my family had experience with programming or using a terminal (there was an HTML book on discount at the book store). I was able to get started because it was dead simple, and only used tools I was already familiar with: the web browser, Notepad, and regular files.</text></comment>
<story><title>Firefox Local Files Theft – Not Patched Yet</title><url>https://quitten.github.io/Firefox/</url></story><parent_chain><item><author>majewsky</author><text>Is it really that hard to run `python -m http.server` in your repository?</text></item><item><author>mort96</author><text>Learning web programming is amazing, since you can just start writing a .html file and open it in a browser. There is no need to learn how go set up a local http server. Chrome truly is killing that experience; you can&amp;#x27;t even load javascript modules without http involved now outside of Firefox.&lt;p&gt;I really hope Mozilla doesn&amp;#x27;t &amp;quot;fix&amp;quot; this &amp;quot;vulnerability&amp;quot; by destroying the experience of people learning web programming like Google did.</text></item><item><author>est31</author><text>IMO, the approach taken by Chrome and other browsers is over restrictive, basically killing off the file:&amp;#x2F;&amp;#x2F; protocol. Already now it&amp;#x27;s impossible to load wasm files in the file:&amp;#x2F;&amp;#x2F; protocol in Chrome, and I think this also had implications on using wasm in electon.&lt;p&gt;Ultimately, file:&amp;#x2F;&amp;#x2F; is a great, cloud free method of having web pages and applications and it should stay that way instead of forcing everything to be networked and reliant on third party computers or domain names.&lt;p&gt;There are so many reports, documents, etc that live as non-networked html files. E.g. rust documentation (cargo doc --open) is generated as html files on-disk and then just displayed without the need for a webserver. Starting a localhost webserver is in fact &lt;i&gt;less&lt;/i&gt; secure than file because now every user on the computer has access instead of just the users with read-access to the files. This has thankfully been fixed in Chrome OS though.&lt;p&gt;Responsive web apps are not the solution as they still need &amp;quot;seeding&amp;quot; via the network. Maybe some kind of standardized format where you have a glorified zip file with some metadata and when you double click it, it opens in the web browser which starts a web server in the background that runs a specially designated js in that zip file and which can accept usual fetch requests and has read access to the entire zip file. The browser&amp;#x27;s &amp;quot;UI&amp;quot; would then communicate with the server via well-known protocols.</text></item></parent_chain><comment><author>CaptainMarvel</author><text>For someone getting started with programming? Very hard - it steepens the learning curve significantly</text></comment>