Create 2019-06-03--js-core-dev-team-weekly.md #986
Conversation
vasco-santos
requested review from
jimpick,
lidel,
dirkmc,
hugomrdias,
jacobheun,
achingbrain and
daviddias
| - Next: | ||
| - More prep for IPFS Camp | ||
| - Finish Draft of AutoNAT spec and open PR | ||
| - Possibly continue with AutoNAT work in JS (time permitting) |
There was a problem hiding this comment.
@jacobheun is it possible to prioritise the connection prioritisation work as well please 😂? To keep the connectivity magic working well the connection manager should not prune the preload nodes and the switch should actively reconnect to them on disconnect.
There was a problem hiding this comment.
@alanshaw yeah I can re-prioritize any remaining time I have this week and next to that. We're working on a connection manager v2 spec so how this is handled may change, but we can at least get an interim solution in place.
|
|
||
| - @prabhakar | ||
|
|
||
| Looking at minor issues over the past 2 weeks. Finding difficult to contribute to js-ipfs |
There was a problem hiding this comment.
@prabhakar can you keep a note of the issues you're finding difficult to understand and we can fix them up - maybe add as a comment to ipfs/js-ipfs#2061
|
|
||
| ### Questions | ||
|
|
||
| - When should we target DHT being ready for real-world use? (dirkmc question) |
There was a problem hiding this comment.
@dirkmc The original plan was to get this released before IPFS Camp. I've updated the PR to enable it by default to include the dependencies that need to be resolved before it is mergable: ipfs/js-ipfs#1994
My bad - this should have already been documented.
|
|
||
| @jacobheun Things missing need to be in an issue (https://github.com/ipfs/js-ipfs/pull/1994) and testing criteriums. Also considering https://github.com/ipfs/js-ipfs/issues/1459 | ||
|
|
||
| @daviddias It is a really important piece of the puzzle for achieving connectivity magic |
There was a problem hiding this comment.
@daviddias I love the idea of a JS IPFS connectivity magic status page.
| ### Cross team updates | ||
|
|
||
| @lidel (Web Browsers WG) | ||
| - new ipfs-companion with latest [Web UI](https://github.com/ipfs-shipyard/ipfs-webui) shipped to Beta channel: [v2.8.2.78](https://github.com/ipfs-shipyard/ipfs-companion/releases/tag/v2.8.2.788) |
|
|
||
| - How far are we from getting delegated routing deployable? (daviddias question) | ||
|
|
||
| @jacobheun Need to sync with infra, it should be close. |
There was a problem hiding this comment.
@jacobheun if we can get the infra sorted what else needs to happen to get this enabled in JS IPFS in the browser by default? Can we get an issue opened in JS IPFS with action items 🙏? Can @vasco-santos help at all with this?
There was a problem hiding this comment.
Added ipfs/js-ipfs#2155. Coordinating the go-ipfs deploy is the biggest blocker for this. Configuration should go pretty quickly. If someone can assist with coordinating that deploy it would be helpful.
There was a problem hiding this comment.
I can help with that coordination. Who is responsible for the infrastructure in the ipfs team?
There was a problem hiding this comment.
@mburns, @Stebalien, can you help here?
There was a problem hiding this comment.
I and @jacobheun synced with @mburns and we will help us with this! 🎉
| - integrate `interface-connection` proposal | ||
| - [libp2p/js-libp2p-tcp#102](https://github.com/libp2p/js-libp2p-tcp/pull/102) | ||
| - [libp2p/js-libp2p-websockets#82](https://github.com/libp2p/js-libp2p-websockets/pull/82) | ||
| - more async iterators work |
There was a problem hiding this comment.
@vasco-santos can you help us out with shipping delegated content routing and shipping the DHT? It would be rad if you could handle re-providing?
There was a problem hiding this comment.
I will try to get reprovide during this week!
| - Dns resolver for IPNS | ||
| - Blocked: | ||
| - Next: | ||
| - Continue DNS resolver |
There was a problem hiding this comment.
@hugomrdias do you think this will be ready in time for camp?
There was a problem hiding this comment.
//cc @Stebalien who is interested in following this work.
@hugomrdias do you have a doc that describes how this is getting implemented?
No description provided.