Peer-to-peer hypermedia protocol
-
Updated
Jul 28, 2020
{{ message }}
IPFS (InterPlanetary File System) is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files.
In some ways, IPFS is similar to the World Wide Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high-throughput, content-addressed block storage model, with content-addressed hyperlinks. This forms a generalized Merkle directed acyclic graph (DAG).
IPFS combines a distributed hash table, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other, except for every node they are connected to. Distributed Content Delivery saves bandwidth and prevents distributed denial-of-service (DDoS) attacks, a problem common with HTTP.
Peer-to-peer hypermedia protocol
IPFS implementation in JavaScript
Peer-to-Peer Databases for the Decentralized Web
Framework for serverless Decentralized Applications using Ethereum, IPFS and other platforms
Useful resources for using IPFS and building things on top of it
Right now a screenshot is taken and added to IPFS and a link is copied to clipboard, but not added to Files.
https://share.ipfs.io/#undefined, but that could be due to Electron 10 tests - needs analysis
A distributed, serverless, peer-to-peer chat application on IPFS
The JavaScript Implementation of libp2p networking stack.
Distributed Application Starter: Vue front-end, Ethereum / IPFS Backend
Content-addressable, peer-to-peer method of storing and sharing images on the internet.
I'd like IPFS companion to use a local gateway without exposing a local IPFS API endpoint. Unfortunately, if I do this, companion will direct all dnslink queries to the public gateway because my local IPFS node "has no peers".
If I configure companion to use a specific IPFS gateway, I expect it to always use that gateway.
There is a minor misspelling in the source file qri/api/context.go. The word "collissions" on line 14 should be changed to "collisions".
Note: Need to wait until ipfs-shipyard/ipfs-webui#1615 is merged to avoid throwing more conflicts on that PR's pile.
Standardize visual presentation of modals throughout Web UI, including the following:
A p2p, secure file storage, social network and application protocol
The simplest way to send your files around the world using IPFS.
This is the main tracking issue for DNSLink support. If there is a programmable DNS service out there, we should have support for it.
Ideally even doing things like detecting the provider from the domain name and doing the right thing.
| Pinning Service | Status |
|---|---|
| CloudFlare | |
| DNSimple | |
| Digital Ocean |
This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:
http/README.md has no tutorial on how to try out ipfs-httpipfs-http supports only `iOpenBazaar 2.0 Desktop Client (talks to openbazaar-go server daemon)
Decentralized Status Page
If a user writes a subgraph referencing contract addresses from (for example) a testnet, and then accidentally deploys the subgraph to a graph node running mainnet, the subgraph will run but won't find any events. We can provide a better experience using eth_getTransactionCount to check that the contract addresses exist on
Content-addressed, authenticated, immutable data structures
Please add a sign up button to main page.
Search engine for the Interplanetary Filesystem.
A music player that connects to your cloud/distributed storage.
This meta issue contains various ideas that may never be implemented, it's a good place to put things that could create useless noise in the issues section