IPFS / IPFS

This tutorial goes over how to use the IPFS command line API to experience IPLD pathing features which allow you navigate a directed acyclic graph (DAG). We will be navigating the DAG of the ipld.io website that is hosted on IPFS.

This content is created as a part of Protocol Labs' Launchpad program. You can get resources and written instructions in our learning platform at https://curriculum.pl-launchpad.io

See all links, commands, and instructions in the tutorial at https://curriculum.pl-launchpad.io/tutorials/ipld/ipld-pathing/
Join Protocol Labs Launchpad: https://pl-launchpad.io/

Chapters:
0:00 Introduction
00:47 Install IPFS
02:21 Install jq
03:20 Find the CID for ipld.io website
03:53 Inspect the Root
05:12 Load a Page With IPFS Pathing
06:00 Dive Deep into a DAG
07:356Load a Page With IPLD Pathing
08:45 Switching Codecs
10:25 Recap

Presentation: Supporting Web Archiving via Web Packaging
Speaker: Sawood Alam @ibnesayeed

Notes
* From Old Dominion University
* Web Packaging … not currently suitable for archiving
* Web Packaging will “bundle” a bunch of web requests and deliver them to a web browser in a single signed exchange
* Signing is different from encryption
* Signing is more suitable for non-private communication
* WARC is a format for storing request/responses for archiving
* Largest crawling tool is Heritrix from Internet Archive - misses a lot of resources (doesn’t recognize JavaScript) - other tools archive more, but are slower
* Server side rewriting … archives need to be modified to be played back on different origins
* Proxy based rewriting is another approach where it appears transparent to the user (eg. oldweb.today)
* Archives are often displayed in ways in which they never existed
* It would be great is browsers natively supported “Memento Timegate”
* Proposals: TimeGate/Named Cache for Loading
* Fixity - no way to prove non-repudiation (eg. Internet Archive was accused of modifying an archive)
* Signed Exchanges only last for 7 days
* Temporal validations: verify that a signature was valid in the past
* Would also like native Memento support in web browsers

Agenda:
- Q2 Accomplishments
- Q2 Challenges
- Q3 Structure
- Q3 Priorities

Q3 OKRs: https://docs.google.com/spreadsheets/d/1AiNUL7vK5Jp8aa839UaMaI_AlBU5r6Bor-A40179I2A/edit#gid=1681757723
[P0] IPFS as a Service
[P0] Testing Infra
[P1] Project Operations
[P1] Package Managers
[P2] Documentation

## Testing Census Meeting Notes
Benchmarks of js-ipfs up again!
All benchmark data relatively level - no observed performance hit
Running this within network testing pipeline could trigger this api, and spawn this job and input into unified metrics database (in addition to here)
Want more control in our own UI to display relative info in a comparative fashion (maybe that allows you to drill down in grafana)
Grafana good for time series, not for compare against baseline we choose
Meta objective: every group should have an MVP with ZERO dependencies on other groups - the stage 2 or 3 can dovetail and merge with a shared vision - however the first step that will block development should be separable from everyone else’s work
Doesn’t give nice overall view - but can be tweaked
Nice thing this *doesn’t* have is go-nightly or something like that to use in tests
Test infra - want specific test cases being run to extract metrics of interest
Want to see greens, yellow, and reds to make it clear where we should put attention to
Want it to be that any community engineer can see health on various go and js commits against other implementations (hard with grafana)
Alan will put a baseline of work into js benchmarks to make it useful for go, and then go from there
What does everybody actually need?
- project operations and package mangers need benchmarks they can use for their specific testing / feedback loops (and need to be able to start running this prior to test infra work completing
- Gateway team wants to be responsible for spinning up nightly mirrors and similar
- Testing pipeline that will hopefully be an orchestrator and aggregator
Using, adapting, and adopting benchmarks using js test suite to cover all the things we want
Alan get go tests running, steven add go tests
Kubernetes repo also has a whole series of go tests written in yaml-based dsl
Package manager tests will likely be shell scripts to import real world data
Current benchmark format looks good for v1 is good, also ability to run locally so can do it on branch

Presentation: wab.ca and wabac.js
Speaker: Ilya Kreymer - https://github.com/ikreymer

Notes
* Ilya runs webrecorder.io
* Hosted web service that records traffic for archiving as the user browsers around
* Part of a grant funded non-profit called Rhizome
* Wab.ac is completely client side player for WARC files using service workers
* Any WARC file can be played back completely in the browser
* Can play wab.ac inside Internet Archive Wayback machine
* Also support .har files (built into the browser) - create in Chrome devtools

Questions
* Who is funding? Webrecorder.io grant from Mellon Foundation - files hosted on WebRecorder.io (2 year grant)
* Data can be stored anywhere and rendered completely in the browser
* Challenges public vs. private? Webrecorder.io is private by default. Possible for somebody to archive private social media
* Client side archiving is not possible yet in a browser without an extension
* Ibnesayeed: WARCreate is another tool for creating WARC files … missing piece is discovery. Opportunity to integrate IPFS for discovery. - Think it would be ideal to integrate with a separate discovery layer. Integration with js-ipfs would make a lot of sense.
* Ibneysayeed was in D.C. at the Web Packaging workshop … pages could run as the original domain.
* All the position papers from the ESCAPE workshop: https://www.iab.org/activities/workshops/escape-workshop/
* Signed exchanges are good for verification and trust
* Marcin: If anyone wants to follow, I am gathering notes about different ways of Mirroring Web to IPFS: https://github.com/ipfs/in-web-browsers/issues/94 (started as ideas for our browser extension)

Discover libp2p, a modular and extensible networking stack which solves many challenges of peer-to-peer applications.

For more information on libp2p
- visit the project website: https://libp2p.io/
- or check out the project GitHub: https://github.com/libp2p

For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS

Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5

Announcement: https://protocol.ai/blog/ann-filecoin-token-sale-and-new-paper/
Coinlist: https://coinlist.co/
Filecoin Paper: https://filecoin.io/filecoin.pdf