Steve Loeppky

@wemeetagain : is there an estimate on when this will be completed? I'm asking because am hoping Lodestar can use the "canary" version of js-libp2p to provide feedback on the...

Thanks for sharing @wemeetagain . No expectation to respond as don't want to create extra work, but if there's a place can point to, I'd be interested in knowing what...

@lidel : can/should we add a regression test for this so we don't do releases that fail for this usecase?

The blog post for this event is being published via https://github.com/ipfs/ipfs-blog/pull/309

For reference the notes that were used to generate the public blog post and the list of action items is here: https://www.notion.so/pl-strflt/2021-08-20-ipfs-io-outage-Post-Mortem-d3937d6992fc4822be554807209f5fb9

Polls were created: #471 #473

For additional naming discussion we have: 1. https://airtable.com/app5roantDlNn9qeE/tblAac2zr6ouqv2lp/viwaNB3PirIVPorWH/reca3AijHgnclwB2K?blocks=hide 2. https://protocollabs.notion.site/IPFS-Naming-2222fd426482499187ede56fcadc11bf

2022-01-05: this didn't get off the ground beyond setup during lab week 2021. Minor, but when it gets picked back up, it may worth moving this to discuss.ipfs.io rather than...

For anyone watching, the "What is the scope here? Are we renaming binaries, repos, etc.?" section was updated to reflect the latest thoughts / proposal of the go-ipfs renaming effort....

Renamed from "Renaming ipfs implementations 2021Q4 edition" to account for this work happening in 2022Q1.