-
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,184 public repositories matching this topic...
-
Updated
Sep 14, 2020 - JavaScript
-
Updated
Sep 12, 2020 - JavaScript
-
Updated
Sep 14, 2020 - JavaScript
-
Updated
Sep 8, 2020 - HTML
On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.
For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce
-
Updated
Jul 17, 2020 - Shell
-
Updated
Oct 31, 2019
-
Updated
Sep 14, 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".
See conversation on ipfs-shipyard/ipfs-webui#1599 (comment)
-
Updated
Sep 14, 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 |
More interop tests
Since we can now run interop tests against go-ipfs and js-ipfs quite easily, we could adjust some of our existing tests so that they automatically become interop tests with the right feature turned on.
Consider the recent changes to [tests::connect_two::connect_two_nodes_by_addr](https://github.com/rs-ipfs/rust-ipfs/blob/master/tests/connec
-
Updated
Feb 13, 2018 - JavaScript
-
Updated
Sep 11, 2020 - JavaScript
-
Updated
Sep 15, 2019 - JavaScript
We have types in various places that do not follow the Rust naming conventions. A good example are all the GraphQL* types that should be spelled GraphQl* to follow the conventions.
It would be nice to clean this up by renaming all types that don't follow the rules.
Marking this as a "good first issue", as it's low-hanging fruit and would be a good way for new contributors to contribute somet
-
Updated
Sep 14, 2020 - JavaScript
-
Updated
Sep 13, 2020 - Go
Sign up button
Please add a sign up button to main page.
-
Updated
Sep 10, 2020 - Elm
This package generates banners, used by our CLIs and also in some external repos :)
You can open new PRs against this file: https://github.com/berty/berty/blob/master/go/pkg/banner/quote.go