IPFS is a distributed peer to peer system. There is no central server! Typically, each machine (peer) runs a daemon that communicates with other peers.
The IpfsClient provides a simple way for your program to access the daemon via the IPFS HTTP API protocol. The client should be used as a shared object in your program, much like HttpClient. It is thread safe (re-entrant) and conserves sockets and TCP connections when only one instance is used.
public class Program
{
static readonly IpfsClient ipfs = new IpfsClient();
public async Task Main(string[] args)
{
// Get the Peer info of the daemon
var peer = await ipfs.IdAsync();
}
}
The Core API is a set of interfaces to IPFS features and is implemented by the client. The FileSystem and PubSub features are most often used.
const string filename = "QmXarR6rgkQ2fDSHjSY5nM2kuCXKYGViky5nohtwgF65Ec/about";
string text = await ipfs.FileSystem.ReadAllTextAsync(filename);
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4