-
Updated
Jul 28, 2020
IPFS

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.
Here are 1,199 public repositories matching this topic...
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Sep 18, 2020 - JavaScript
-
Updated
Sep 28, 2020 - JavaScript
-
Updated
Sep 8, 2020 - HTML
I was looking into starting go-ipfs with additional flags: --enable-pubsub-experiment
(pubsub) and --enable-namesys-pubsub
(IPNS over pubsub) and the main concern I've found was use of resources:
In order to enab
-
Updated
Jul 17, 2020 - Shell
-
Updated
Oct 31, 2019
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Mar 24, 2018 - JavaScript
-
Updated
Apr 10, 2020 - TSQL
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".
As mentioned in ipfs-shipyard/ipfs-webui#1649 (comment), the links for issues/GH/etc drop off at 768h resolution in Brave with Linux furniture. Tighten height slightly to make room.
-
Updated
Oct 1, 2020 - Java
-
Updated
Aug 24, 2020 - JavaScript
-
Updated
Sep 9, 2020 - Go
Summary
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.
Status
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 outipfs-http
ipfs-http
supports only `i
-
Updated
Oct 1, 2020 - JavaScript
-
Updated
Feb 13, 2018 - JavaScript
-
Updated
Sep 15, 2019 - JavaScript
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
-
Updated
Oct 1, 2020 - JavaScript
Sign up button
Please add a sign up button to main page.
-
Updated
Sep 26, 2020 - Go
-
Updated
Sep 21, 2020 - Elm
[META] Ideas 💡
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
Doc
- add various demonstration gifs in README.md files (#2080)
- add graphs (flow, DAG) to explain some particular parts
Code Quality
- switch moment.js usage to day.js and remove moment.js (#2174)