Create 2019-01-02--gui-and-in-web-browsers-weekly.md #821
Conversation
ghost
assigned 
| - Added a warning about mixed-content when gateway URL is not a Secure Context - [ipfs-companion/pull/650](https://github.com/ipfs-shipyard/ipfs-companion/pull/650) | ||
| - Started discussion about the future of DNSLink cache - [ipfs-companion/pull/646](https://github.com/ipfs-shipyard/ipfs-companion/pull/646#issuecomment-450879014) + [go-ipfs/issues/5884](https://github.com/ipfs/go-ipfs/issues/5884) | ||
| - Next: | ||
| - Finalize OKRs |
There was a problem hiding this comment.
@daviddias draft is in the 'wb' spreadsheet, if anything looks off would appreciate feedback as inline comments there or in #804 :)
There was a problem hiding this comment.
I just went through the KRs and posted a couple of comments. I believe there is room to enhance them with more real/current users interaction
| - Started discussion about the future of DNSLink cache - [ipfs-companion/pull/646](https://github.com/ipfs-shipyard/ipfs-companion/pull/646#issuecomment-450879014) + [go-ipfs/issues/5884](https://github.com/ipfs/go-ipfs/issues/5884) | ||
| - Next: | ||
| - Finalize OKRs | ||
| - tackle holiday backlog |
| - JS IPFS 0.34 release dance 💃 | ||
| - Holidays | ||
| - Blocked: | ||
| - JS IPFS 0.34 release blocked on stack overflow issues with latest libp2p |
There was a problem hiding this comment.
Are these issues documented? Could you link them here please?
There was a problem hiding this comment.
Will DHT be part of this release again?
There was a problem hiding this comment.
Just one issue: https://github.com/libp2p/js-libp2p-switch/issues/287
PRs resolving it:
- clean up sync in async usage libp2p/js-libp2p-switch#297
- nextTick instead of setImmediate, and fix sync in async libp2p/js-libp2p-crypto#136
- avoid running sync code in asynchronously js-ipfs-bitswap#184
This was discovered only when getting interop tests in good shape for the 0.34 release: ipfs/interop#51
As of right now, DHT is still not part of this release. Once we get the interop tests back in good shape we can evaluate how much work is remaining on the DHT endeavour.
| - JS IPFS 0.34 release blocked on stack overflow issues with latest libp2p | ||
| - Next: | ||
| - Cool stuff coming to a JS IPFS near you: | ||
| - Way smaller bundle is coming <https://github.com/ipfs/js-ipfs/pull/1795> minified+gzip >50% smaller! |
| - Way smaller bundle is coming <https://github.com/ipfs/js-ipfs/pull/1795> minified+gzip >50% smaller! | ||
| - DHT is coming! <https://github.com/ipfs/js-ipfs/pull/856> APPROVED - blocked on test failures | ||
| - Fast `ipfs.add` is coming <https://github.com/ipfs/js-ipfs-unixfs-importer/pull/10> | ||
| - > In real-world use, this changed the time it takes to \`jsipfs add\` a 260MB file to a fresh repo from 13.7s to 1.95s. By comparison\`go-ipfs\` takes 1.58s to add the same file to a fresh repo. |
There was a problem hiding this comment.
@alanshaw @achingbrain how do the interop tests compare with this new change? It might have been that the previous 1/4 the speed to transfer a large file was largely bottlenecked by just adding the file itself.
There was a problem hiding this comment.
Wow yes good point, looking at the test code, the add is done inside the test and not before so we should see an improvement 🏃💨
| - \[Live] Restructured ProtoSchool website to include community info <https://github.com/ProtoSchool/protoschool.github.io/pull/103> | ||
| - \[Merge pending review] Added a text-based tutorial on underlying concepts <https://github.com/ProtoSchool/protoschool.github.io/pull/59> | ||
| - Next: | ||
| - Seek volunteers to lead chapters so there’s more content at launch |
There was a problem hiding this comment.
@terichadbourne suggestion: What about pinging the folks that already organize IPFS Meetups all over the place?
There was a problem hiding this comment.
@daviddias That's in my plans to tackle after launch. For now I'm focusing on PL folks who can serve as guinea pigs for my chapter setup process before I reach out more broadly. :)
There was a problem hiding this comment.
I see! Here is my attempt: Ping fabulous people of London @olizilla, @achingbrain @alanshaw and spetacular people of Porto @marcooliveira @satazor @vasco-santos @hugomrdias et al (you are really many), both purveyors of really awesome meetups, would you be so kind to respond to the ProtoSchool call? :D
There was a problem hiding this comment.
The London crew has already stepped up. 🎉 A Porto chapter would be awesome if the folks there have the time and interest!
There was a problem hiding this comment.
hey hey, let's chat! How can we get the conversation going? Maybe schedule a call?
cc #790