owned this note
owned this note
Published
Linked with GitHub
## IPFS Stewards <> Advocates sync notes 14.10.2022
### Attendees
- Reid
- Mosh
- Lidel
- Jorropo
- Daniel
- Discordian
- Steve
- Elliot
### Discussion topics
- @discordian How to advance https://github.com/libp2p/go-libp2p-relay-daemon/issues/18
- For "Create a Simple Chat App" we heavily utilize CircuitRelayV1, since it was removed from Kubo, we looked at using libp2p-relay-daemon, but haven't been able to connect to it from the JS side in browser (or desktop).
- It sees we have a bug related to Secure websockets in go-libp2p that touches TLS termination
- One bug related to WS that is present in Kubo 0.16 https://github.com/libp2p/go-libp2p/pull/1829
- WebTransport is now available in js-ipfs. It will likely be released as part of the upcoming js-libp2p release this coming monday. Example (https://github.com/libp2p/js-libp2p-webtransport#libp2p-usage-example)
- 🎬 @biglep: figure out what we need to do get proper regression tests in place for go-libp2p and Kubo so that CI breaks when we're broken like this.
- Daniel IPFS Roadmap & Advocates plan for Q4
- Additional notes from Mosh based on conversations with Daniel, Biglep, Lidel, Dietrich, Reid, JB, Molly
- Reposition IPFS as a production-grade solution for key problems with building on today’s web, vs. a cool thing for hackers to try. Improve our internal understanding, & then communication, of what 2-4 use cases IPFS is great at solving, then double down on features, messaging, and devrel for those.
- Most devs want end-to-end example apps that showcase the power & capabilities of IPFS (docs & blogs today often focus on 1 feature at a time, which is harder to translate into practice). 2 examples are coming soon :)
- Accelerator & seed-stage teams need stronger & more personal technical guidance for making tradeoffs & decisions.
- On-ramps for learning & contributing are hard to navigate
- Everything should be slightly uncomfortably open (example: roadmap docs themselves)
- Specs feel abandoned. IPIP is a good first step.
- Docs has accumulated a lot of duplicate material
- Smaller-contributions: lacking contributor guides, good first issues, etc.
- “Even if we invite people to the restaurant, there are no chairs.”
- Traffic on our owned properties is very, very low – a good IPFS blog post gets 300 views. Need to take this show on the road, to conferences beyond Web3, popular programming podcasts, etc.
- What are they key quesitons we want to answer?
- Getting insight on IPFS reposition around production scale / converge on 2-4 killer use cases
- Pull out what the details are and what are the gaps
- Understanding others experience contributing to the project
- Personas
- Contributors
- Operators
- Consumers / app builders on top
- Another option: going to the other tracks and listening what users are saying like "DeSci"
- Analytics
- https://plausible.io/docs.ipfs.tech
- @Jorropo unixfs talk at IPFS Camp
- Looking for a track to speak at
- Planning to discuss light IPFS clients & UnixFS
- Would need about a 15 minute talk duration