https://bugzilla.mozilla.org/show_bug.cgi?id=1354807 Bugzilla Quick Search [ ] * Browse * Advanced Search * Reports * * Documentation * New Account * Log In Sign in with GitHub or [ ] [ ] [password ] [*] Remember [Log in] * Forgot Password [ ] [Reset Password] [moz] * Mozilla Home * * Privacy * Cookies * Legal Please enable JavaScript in your browser to use all the features on this site. Copy Summary [ ] View V * Reset Sections * Expand All Sections * Collapse All Sections * * History * * JSON * XML Open Bug 1354807 Opened 4 years ago Updated 3 hours ago Support for the IPFS protocol Summary: Support for the IPFS protocol Categories (Core :: Networking, enhancement, P3) Product: Core V Core Shared components used by Firefox and other Mozilla software, including handling of Web content; Gecko, HTML, CSS, layout, DOM, scripts, images, networking, etc. Issues with web page layout probably go here, while Firefox user interface issues belong in the Firefox product. (More info) See Open Bugs in This Product File New Bug in This Product Watch This Product Component: Networking V Core :: Networking For bugs in Mozilla's modular networking library (aka "Netlib" or "Necko".) The networking library supplies the software interface that Mozilla uses to access physical transports (e.g. the Internet and local drives), perform URL resolutions, and handle a variety of networking protocols. Examples of appropriate bugs: URLs with backslash not fetched; URLs starting with a single slash turn into http:///; Cannot access authenticated FTP site. See Open Bugs in This Component Recently Fixed Bugs in This Component File New Bug in This Component Watch This Component Version: 52 Branch Platform: Unspecified Unspecified Type: enhancement Priority: P3 Severity: normal Points: --- Tracking () Status: UNCONFIRMED Status: UNCONFIRMED --- Mark as Assigned Milestone: --- Iteration: --- Project Flags: Webcompat Priority [---] Root Cause [---] a11y-review [---] user-doc-firefox [---] Fission Milestone [---] Tracking Flags: Tracking Status relnote-firefox [---] thunderbird_esr78 [---] [---] firefox-esr78 [---] [---] firefox84 [---] [---] firefox85 [---] [---] firefox86 [---] [---] People (Reporter: sonichedgehog_hyperblast00, Unassigned) Assignee: Unassigned Assignee: [ ] Reset Assignee to default Mentors: --- QA Contact: [ ] Reset QA Contact to default Reporter: # sonichedgehog_hyperblast00 Triage Owner: # jstutte CC: 20 people References Depends on: --- Blocks: --- Regressions: --- Regressed by: --- URL: See Also: 1312153 Details (Whiteboard: [necko-backlog]) Alias: --- Keywords: --- Whiteboard: [necko-backlog] QA Whiteboard: --- Has Regression Range: --- Has STR: --- Votes: 3 Bug Flags: behind-pref [ ] firefox-backlog [] sec-bounty [ ] sec-bounty-hof [] in-qa-testsuite [ ] [ ] in-testsuite [ ] qe-verify [] Crash Data Signature: Security (public) This bug is publicly visible. User Story Bottom | Tags V * Reset Timeline V * Reset * * Collapse All * Expand All * Comments Only sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Description * 4 years ago User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170317000000 Steps to reproduce: This ticket is intended to discuss the status of IPFS support, and progress on implementing it as a supported standard within Firefox. Brief description: IPFS is a new web protocol aiming to replace HTTP. It uses a mix between torrent and blockchain technology; This allows websites to be seeded by their viewers rather than being hosted on a central server, while at the same time the owner maintains editing rights through the use of private keys. This not only increases network speed and efficiency, but makes websites entirely censorship and DDoS resistant... considering they aren't hosted on any central server, and will be available as long as at least one peer remains online. Why Firefox should support this: IPFS promises to be a revolutionary technology for multiple reasons; Increasing network speeds worldwide, removing all hosting costs, and making websites secure from government censorship. However, for this standard and its goals to succeed, major websites and web browsers alike must adopt it; The average internet user won't be interested in visiting a site that requires special browsers or third-party addons to access. I suggest that Firefox does its part in mainstreaming this standard... by allowing the browser to access websites hosted through the IPFS protocol, as well as caching and seeding web pages from within the browser. Although the technology is still in early stages, it's likely to replace the HTTP protocol and eventually become the new standard... by supporting it, Firefox can be among the first browsers to understand and aid this visionary approach. More info on IPFS: https://ipfs.io https://github.com/ipfs/ipfs https://en.wikipedia.org/wiki/InterPlanetary_File_System More info on ZeroNet: https://zeronet.io https://github.com/HelloZeroNet/ZeroNet https://en.wikipedia.org/wiki/ZeroNet YF (Yang) Updated [517] * 4 years ago Severity: normal - enhancement Component: Untriaged - Networking Product: Firefox - Core Dragana Damjanovic [:dragana] Updated [91b] * 4 years ago Whiteboard: [necko-backlog] sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 1 * 4 years ago Something I feel I need to make clear, as I believe I haven't in my initial posting: As its own developers have stated, IPFS and ZeroNet are still in an early stage of development, and as such not even the full specifications have been defined. My suggestion should not be interpreted as something that must be fixed tomorrow, but rather an ongoing effort to prepare Firefox for approaching this new web architecture from the browser side. On the other hand, please don't let this aspect put the initiative off the priority list. As a reminder, IPFS is being backed up by Tim Berners-Lee, the very creator of the World Wide Web! IPFS is not the garage project of a random development team, but a serious worldwide initiative to rebuild the web and fix some of its current major flaws. Valentin Gosu [:valentin] (he/him) Comment 2 [ded] * 4 years ago Hi, thanks for your suggestions. We are aware of the potential of IPFS and are watching its development closely. We will address this topic next week at our networking team meeting. sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 3 * 4 years ago (In reply to Valentin Gosu [:valentin] from comment #2) That's very wonderful to hear! Thank you for looking into it. lgierth Comment 4 [eae] * 4 years ago @(In reply to Valentin Gosu [:valentin] from comment #2) > Hi, thanks for your suggestions. We are aware of the potential of IPFS and > are watching its development closely. > We will address this topic next week at our networking team meeting. Would it be useful if I joined and gave an update on the browser-related work that IPFS has seen in Q1? Main areas have been URLs, js-ipfs node running in WebExt, and interop with non-browser nodes. Patrick McManus [:mcmanus] Comment 5 [2b0] * 4 years ago I think we have what we need atm. thanks. YF (Yang) Updated [517] * 4 years ago See Also: - 1312153 Firefox Bug Husbandry Bot Comment 6 [963] * 3 years ago Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258 Priority: -- - P1 Firefox Bug Husbandry Bot Comment 7 [963] * 3 years ago Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258 Priority: P1 - P3 archael87 Comment 8 [c62] * 3 years ago I'd like to add the Shift project. Currently they are using "jenga" they created to convert dns traffic to IPFS. They launched their new decentralized website using IPFS on 1/1/2018. This will be a platform for hosting IPFS content. shiftnrg.org sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 9 * 3 years ago (In reply to archael87 from comment #8) That is useful information and a good service to keep track of. Thank you for mentioning! For the purpose of this report, I'm focusing on a native IPFS implementation. To my understanding this primarily includes: - A builtin version of the IPFS daemon, for users who do not have IPFS installed system wide. - A console or special page (eg: about:ipfs) allowing IPFS commands to be input (eg: ipfs add filename). - Implementation for the js-ipfs interface, allowing IPFS specific JavaScript functions to execute from websites. Note that I'm not a specialist in how exactly they should be implemented by the browser. I simply believe they should in order to encourage and mainstream early adoption of this fantastic technology. Although IPFS is still getting there, it has matured quite a bit over the past few months from what I've seen. Currently I see no reason why it wouldn't become at least as popular as the FTP protocol in the following years, if not much more rather quickly. As such, I'm personally in favor of the idea that a builtin version of the daemon deserves at least an experimental implementation accessible from about:config for the time being. If that is considered too much, perhaps a separate branch / nightly build would be an even safer place to experiment with that, depending on the policies of those builds. sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 10 * 3 years ago Something useful I forgot to mention: Work is already being done to implement IPFS for Firefox using an addon. This addon is called IPFS Companion, and can be found on the official addons website: https://addons.mozilla.org/en-US/firefox/addon/ipfs-companion/ Currently the extension itself doesn't do much: It offers an icon which allows you to see the status of and issue commands to the IPFS daemon running on your system. Other versions of the extension intended for different browsers (eg: Brave browser) come with a portable version of the daemon, which I understand is planned for both Firefox and Chrome once it's possible to get it working through WebExtensions. Hopefully that addon can serve as inspiration for a native implementation, making the work on such easier. I'd suggest keeping it handy and tracking updates, especially if it will support a builtin daemon at a later date. sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 11 * 3 years ago I'm happy to announce that the IPFS Companion extension has finally added support for embedded IPFS nodes via js-ipfs to the Firefox version. It now provides builtin IPFS functionality directly within the browser, with no need to run go-ipfs system wide in order to access the network. You still need to use a public gateway for the time being (https://ipfs.io/ipfs/ rather than http://127.0.0.1:8080/ipfs/) but I understand this inconvenience will also be fixed later. I'm hoping this gets us closer to a native implementation of IPFS under Firefox and Chromium, once the code becomes ready for mainstream usage and can be implemented as a default browser feature. Very excited to see how it goes. sonichedgehog_hyperblast00@yahoo.com Reporter [cbd] Comment 12 * 3 years ago A huge thank you to Mozilla for adding native support for the ipfs:// protocol in Firefox 59! While this isn't a native implementation, it definitely gets us closer to that point, while in the meantime the IPFS Companion extension will have an easier time offering important features to the browser. Clay Ferguson Comment 13 [294] * 3 hours ago IMO, saying "a new web protocol aiming to replace HTTP" is completely incorrect and will cause probably 99% of people unfamiliar with IPFS to immediately believe they don't like it. Nobody wants to replace HTTP, and especially not the IPFS community either. What IPFS will be is a new protocol like scp or ftp, etc., that will let the browser retrieve data that may contain HTML, or may contain just data for resources like images, files, videos, etc. You need to log in before you can comment on or make changes to this bug. Top |