adam/ipfs-blog
1
0
Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-07-04 00:41:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update web3-browsers-for-decentralized-storage.md

Browse Source 
Fixing some untrue / confusing statements.
This commit is contained in:
Marcin Rataj
2022-01-26 14:13:01 +01:00
parent b9c5efe0b0
commit c8450bcf2d
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/web3-browsers-for-decentralized-storage.md
+8 -8
View File
@@ -25,28 +25,28 @@ Brave [announced](https://blog.ipfs.io/2021-01-19-ipfs-in-brave/) native IPFS su
Opera also [supports](https://blog.ipfs.io/2021-02-08-opera-ios-and-ipfs/) IPFS on iOS, Android, and Windows, adding to the number of browsers implementing the protocol. Browser integration on desktops is sufficiently underway, and the work that is happening there will trailblaze the next phase of development: mobile support. Currently, the amount of resources needed to spin up an IPFS node is more than what most mobile browsers can access, so the protocol is being updated to support lighter environments.
## The Migration from HTTP to Web3
## The Migration from Centralized HTTP to Web3
Browsers operate on HTTP natively and IPFS operates on significantly different protocol schemes. This means the evolution to Web3 and decentralized storage will be slow but steady. Core to understanding why this migration is a gradual process is the knowledge of how data is stored under a Web3 paradigm.
Currently, decentralized storage solutions such as IPFS require centralized HTTP gateways to access data. One of the goals for data migration from HTTP to Web3 is to ensure that this data remains accessible in a completely decentralized way, with no single points of failure. By integrating IPFS into browsers, it is possible for Web3 infrastructure to interact with browsers seamlessly and can bring that kind of resiliency.
Currently, decentralized storage solutions such as IPFS require centralized HTTP gateways to access data. One of the goals for data migration from this intermediate stage to Web3 is to ensure that this data remains accessible in a completely decentralized way, with no single points of failure. By integrating IPFS into browsers, it is possible for Web3 infrastructure to interact with browsers seamlessly and can bring that kind of resiliency.
## Standardization and Interoperability
Traditional file systems are notoriously bad with interoperability. Companies have a vested interest in keeping their ecosystems siloed and eschewing UX efforts to allow consumers to easily transfer files in between systems.
As an open standards ecosystem, however, the decentralized web offers a way to increase interoperability since all browsers would need to get their data from decentralized gateways. At the moment, much of the interaction between browsers and decentralized gateways happens through extensions. Browser extensions allow for user choice.
As an open standards ecosystem, however, the decentralized web offers a way to increase interoperability since all browsers would need to get their data from decentralized gateways. At the moment, much of the interaction between browsers and decentralized gateways happens through extensions such as [IPFS Companion](https://docs.ipfs.io/install/ipfs-companion/). Browser extensions allow for user choice.
Today’s extensions, however, are just a step on the roadmap to full browser integration. Browsers have a tendency to limit the functionality of extensions, demonstrating the need for native support for IPFS.
Today’s extensions, however, are just a step on the roadmap to full browser integration. Browsers have a tendency to limit the functionality of extensions, demonstrating the need for native support for IPFS and [content addressing](https://docs.ipfs.io/concepts/content-addressing/).
## Opportunities and Challenges for Decentralized Storage in Browsers
As mentioned before, Brave and Opera support IPFS natively, either through an HTTP gateway or a full node. These implementations are in their infancy, and there are opportunities that have arised for future development, namely user experience.
As mentioned before, Brave and Opera support IPFS addresses natively, and Brave allows their resolution either through an HTTP gateway or a full node. These implementations are in their infancy, and there are opportunities that have arised for future development, namely user experience.
Today, these browsers don't have the most intuitive UX when interacting with IPFS nodes and decentralized gateways, primarily because they’ve been designed for HTTP. Protocol Labs has been working with Brave on a browser user experience that is designed specifically for IPFS.
Today, these browsers don't have the most intuitive UX when interacting with IPFS nodes and decentralized gateways, primarily because they’ve been designed around client-server model, and lack peer-to-peer concepts and UI metaphors. Protocol Labs has been working with Brave on a browser user experience that is designed specifically for IPFS.
## Just the Start
Decentralized storage is well on its way to becoming standard across Web3. Browsers will continue to pave the road for mass adoption of decentralized storage solutions like IPFS. What browsers offer is a “front door” to Web3 for internet users. The vision is for decentralized storage to be natively integrated with browsers such that everyday users are exposed to Web3 without needing to make conscious decisions and tackle brand new interfaces.
Content addressing and decentralized storage are well on its way to becoming standard across Web3. Browsers will continue to pave the road for mass adoption of decentralized storage solutions like IPFS. What browsers offer is a “front door” to Web3 for internet users. The vision is for decentralized storage to be natively integrated with browsers such that everyday users are exposed to Web3 without needing to make conscious decisions and tackle brand new interfaces.
Over the last year, IPFS has made leaps and bounds in its integration and acceptance among the browser ecosystem. Working alongside Brave, Opera, and others, Protocol Labs continues to innovate, spot opportunities, and grow.
Over the last year, IPFS has made leaps and bounds in its integration and acceptance among the browser ecosystem. Working alongside Brave, Opera, and others, Protocol Labs continues to innovate, spot opportunities, and grow.