libp2p Weekly 2025-07-29

[achingbrain]

Meeting time: 15:15 UTC
Meeting link: https://huddle01.app/room/ktc-hnfs-aop
Previous occurrence: #3227

Discussion items

1. Streams Streams as EventTargets #3226
   a. Background: js-libp2p used to use node streams internally when it was a part of js-ipfs (hard to get error handling correct). Moved away from node streams due to error handling. The utility functions from node core makes error handling easier since then (migrated to pull streams - invert control of stream to pull from another source). Switched to use async iterables and this works well but no one else has heard of them and is a barrier of entry for new developers. eventemitters are familiar used in webrtc, websockets, handlers in UIs. Web standard called eventTarget is used every and already used extensively in codebase. See perf section of main issue, WebStreams are slow due to every single operation being async (punting continuation of function to microtask queue which adds cumulative latency). Event handlers are synchronous and perf of event target are better than duplex iterators (which are not all async) and webstreams (Streams can still be made async iterable by implementing the protocol - if less care about performance and want to optimize for readability)
   Perhaps release it in v3 next month after PRs to js-libp2p-gossipsub, yamux, etc.
2. @dozyio Demo!
   a. Chess consensus game dozy.io/chess-bot/
3. Protection from key overwriting in kadDHT #3232

Workstreams Updates

Up next

Community PR Review

Other

1. Any callouts/travel/need help

[p-shahi]

Attendance: @achingbrain @dozyio @p-shahi @dhuseby @acul71