b_1_ipfs-impls.toml

# the name of your event
name = "IPFS Implementations"

# the name of the group organizing the event
org = "PL Starfleet"

# the github handle of the directly responsible individual for this event
# (this person will coordinate with devent organizers)
dri = "@jbenet"

# the website of the event
# make sure to have all the relevant information: dates, venue, program, ticketing (if any), etc.
website = "https://discuss.ipfs.io/t/2022-07-12-ipfs-implementations/14632"

# the start date of the event
date = "2022-07-12"

# how many days the event lasts (1 - N)
days = 1

# the event times (shows up in the event card)
times = "13:00 - 17:00"

# the event venue name (will show up on the event card - TODO)
venueName = ""

# the event venue address (will show up on a map -- TODO)
venueAddress = ""

# the max number of attendees of the event
attendees = "50"


# these is unsued:
# tickets = "Waitlist"

# the "difficulty" of the event -- one of:
# ["Beginner", "Intermediate", "Advanced", "All Welcome"]
difficulty = "All Welcome"

# tags for the event, will show up as labels.
# pick 1-4
tags = ["Talks", "Workshops"]

# a color, to group key events visually. use sparingly
# color="purple"


# a description of the track.
# will show up when the user clicks the event card.
#
# Notes:
# - use a markdown table for the schedule
# - recommended start: 09:00
# - recommended lunch: 12:00 or 13:00
# - recommended end:   17:00
# - use 15m, 20m, 30m, 45m, or 60m session slots
# - use 15m breaks, one in the morning, one or two in the afternoon
#
description = """
This track provides an overview of IPFS implementations. Each presentation is about a different IPFS Implementation, and meant to be a pitch for the implementation to prospective users, contributors, etc. Think of these presentations as listed in a webpage about IPFS implementations.

Each talk should cover:
- What the implementation is for (problems / solutions)
- How it works / architecture
- Team (who's building it)
- Traction so far
- Roadmap
- Painpoints: what the impl is not good at.

(?) - denotes tenative (not confirmed)
"""


[[timeslots]]
startTime="13:00"
speakers=["@jbenet"]
title="IPFS Implementations"
description=""

[[timeslots]]
startTime="13:15"
speakers=["@dietrich"]
title="Lessons from putting IPFS in weird places"
description=""

[[timeslots]]
startTime="13:30"
speakers=["@adin?"]
title="Kubo (go-ipfs)"
description=""

[[timeslots]]
startTime="13:45"
speakers=["@lidel"]
title="IPFS Gateways"
description="Gateways in the past, present, and the future"

[[timeslots]]
startTime="14:00"
speakers=["@lidel"]
title="IPFS Companion, IPFS Desktop, and Brave"
description="Bringing IPFS to the end user"

[[timeslots]]
startTime="14:15"
speakers=["@expede","@matheus23"]
title="WebNative File System (WNFS)"
description="The WebNative File System adds versioning, cryptree-based encryption, and eventual consistency on top of IPFS"

[[timeslots]]
startTime="14:30"
speakers=["@b5"]
title="Iroh"
description="Introducing Iroh: Performant IPFS for the whole world, right now"

[[timeslots]]
startTime="14:45"
speakers=["@hsanjuan"]
title="IPFS Cluster"
description="IPFS Cluster is an P2P application that uses the kubo (go-ipfs) menu with some spices on top"

[[timeslots]]
startTime="15:00"
speakers=[""]
title="Break"
description=""

[[timeslots]]
startTime="15:15"
speakers=["@jbenet"]
title="Filecoin -- an exabyte scale IPFS system"
description=""

[[timeslots]]
startTime="15:30"
speakers=["@arajasek"]
title="Lotus - an IPFS blockchain node"
description=""

[[timeslots]]
startTime="15:45"
speakers=["@mikeal"]
title="Web Scale IPFS"
description="""An brief overview of the read and write pipelines in 
nft.storage and web3.storage implementing IPFS protocols across several 
services and infra providers"""

[[timeslots]]
startTime="16:00"
speakers=["@jlogelin"]
title="Estuary"
description=""

[[timeslots]]
startTime="16:15"
speakers=["@cory"]
title="IPFS Operator"
description="IPFS cluster kubernetes operator"

[[timeslots]]
startTime="16:30"
speakers=["@danieln"]
title="Auspinner"
description="Auspinner is a CLI tool for pinning CARs to Pinning API Spec compliant services using Bitswap."

[[timeslots]]
startTime="16:45"
speakers=[]
title="Break"
description=""

[[timeslots]]
startTime="17:00"
speakers=["@guseggert"]
title="libipfs"
description="libipfs is an upcoming library of IPFS components for building IPFS implementations"

[[timeslots]]
startTime="17:15"
speakers=["@achingbrain"]
title="js-ipfs"
description=""

[[timeslots]]
startTime="17:30"
speakers=["@alari"]
title="Aqua language"
description="Aqua is a π-calculus based language for scripting decentralized protocols on top of libp2p, IPFS and beyond."

[[timeslots]]
startTime="17:45"
speakers=["@ianopolous"]
title="Peergos private filesystem"
description="Peergos builds on IPFS to add quantum-resistant, metadata-protected encryption with Cryptree+, block-level access control with authed-bitswap, and a super minimal ipld daemon with ipfs-nucleus, whilst maintaining autoscaling and efficient modification properties of IPFS."