You read it right, the recordings from IPFS Camp are starting to get out, grab them while they are HAWT 🔥
For this batch we have:
# ⚡️ Lightning Talks (opens new window)
# 📃 Poster Projects (opens new window)
Topic | Owner | Description | Recording |
---|---|---|---|
HTTP gateways (opens new window) | @autonome (opens new window) | An IPFS Gateway acts as a bridge between traditional web browsers and IPFS. | Video (opens new window) |
The intricacies of DWeb Addressing (opens new window) | @lidel (opens new window) | Systems like IPFS use hashes of data to reference content by itself, rather than by an arbitrary location/name. With this comes compatability and human concerns around referencing data. | Video (opens new window) |
IPLD Selectors (opens new window) | @maparent (opens new window) | IPLD Selectors are expressions that identify ("select") a subset of nodes in an IPLD dag. i.e. subsets of IPLD objects. | Video (opens new window) |
Graphsync (opens new window) | @b5 (opens new window) | A protocol to synchronize graphs across peers. | Video (opens new window) |
KeyStore (opens new window) | @gozala (opens new window) | A secure and simple way of storing and managing keypairs (for IPFS services). | Video (opens new window) |
NPM-on-IPFS (opens new window) | @achingbrain (opens new window) | Let's take NPM and put it on IPFS. | Video (opens new window) |
DAG walking facilities in IPLD (opens new window) | @warpfork (opens new window) | The goal of IPLD is to enable decentralized data-structures that are universally addressable and linkable. | Video (opens new window) |
IPFS/libp2p PubSub (opens new window) | @whyrusleeping (opens new window) | Publish-Subscribe, called ‘pubsub’ for short, is a pattern often used to handle events in large-scale networks. | Video (opens new window) |
CRDTs (opens new window) | @parkan (opens new window) | A "Conflict-free replicated data type" is a data structure which can be replicated across multiple computers in a network, without conflicts! | Video (opens new window) |
IPFS Nodes (opens new window) | @carsonfarmer (opens new window) | A general overview of what it means to be/implement an IPFS node. | Video (opens new window) |
IPFS DHT (opens new window) | @gpestana (opens new window) | IPFS uses a Distributed Hash Table (DHT) to keep track of various types of data, such as content provider records. | Video (opens new window) |
Mutable File System (MFS) (opens new window) | @leshokunin (opens new window) | Mutable File System (MFS) is a tool built into IPFS that lets you treat files like you would a normal name-based filesystem. | Video (opens new window) |
Bitswap (opens new window) | @jacobheun (opens new window) | Bitswap is the data trading module for IPFS. Its purpose is to request blocks from and send blocks to other peers in the network. | Video (opens new window) |
PeerPad internals (opens new window) | @jimpick (opens new window) | PeerPad is a decentralized editor that allows concurrent writing of text. | Video (opens new window) |
go-ipfs Infrastructure (opens new window) | @stebalien (opens new window) | This topic should cover what it takes to initialize a go-IPFS node, and connect it to a public P2P network. | Video (opens new window) |
IPFS Cluster (opens new window) | @meiqimichelle (opens new window) | IPFS Cluster is a stand-alone application and a CLI client that allocates, replicates, and tracks pins across a cluster of IPFS daemons. | Video Part-1 (opens new window) Video Part-2 (opens new window) |
Textile internals (opens new window) | @andrewxhill (opens new window) | Textile is a set of tools and trust-less infrastructure for building censorship resistant and privacy preserving applications. | Video (opens new window) |
The design of the IPFS Repo (opens new window) | @dignifiedquire (opens new window) | A repo is the storage repository of an IPFS node. It is the subsystem that actually stores the data IPFS nodes use. | Video (opens new window) |
IPFS/Libp2p content routing (opens new window) | @bigs (opens new window) | The IPFS routing system utilizes "content provider records" hosted on a distributed key-value store to resolve content providers. | Video (opens new window) |
Circuit Relay (opens new window) | @ianopolous (opens new window) | The circuit relay is a means to establish connectivity between libp2p nodes (e.g. IPFS nodes) that wouldn't otherwise be able to establish a direct connection to each other. | Video (opens new window) |
Swarming (concept) (opens new window) | @mburns (opens new window) | Swarming is a software method that takes advantage of multiple peers (the "swarm") to fulfill a task which may be easily distributed. | Video (opens new window) |
IPNS (opens new window) | @aschmahmann (opens new window) | IPNS is a system for creating and updating mutable links to IPFS content. | Video (opens new window) |
# There are more to come, keep posted!
If you are interested in receiving an update when the next calls are out, you can do this in one of the following ways:
- Watch and Star the ipfs/camp repo (opens new window), where all the content will live ad-eternum.
- Subscribe to the RSS feed of this blog (opens new window).
- Subscribe to the IPFS Weekly Newsletter (opens new window) if you are interested in general IPFS updates.
- Subscribe to the IPFS Events Newsletter (opens new window) if you are interested in IPFS events.
Enjoy all the recordings and have a great week!