This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
Create 2019-01-28--js-core-dev-team-weekly.md #852
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
jacobheun
commented
Jan 28, 2019
•
jacobheun
commented
- Add recording url
ghost
assigned 
alanshaw
reviewed
Jan 28, 2019
|
|
||
| @achingbrain | ||
| - Done: | ||
| - npm-registry-client => npm-ipfs-client |
There was a problem hiding this comment.
@achingbrain can we get a link to the PR?
daviddias
reviewed
Jan 29, 2019
|
|
||
| @jacobheun | ||
| - Done: | ||
| - Better custom lock example in datastore s3 [js-datastore-s3#13](https://github.com/ipfs/js-datastore-s3/pull/13) |
There was a problem hiding this comment.
@jacobheun can you work on a blog post to explain how powerful this is? Lot's of people get stuck on "how to use other backends to store" and they are completing missing that js-ipfs already supports this (for more than a year!)
There was a problem hiding this comment.
The blog post should end suggesting that folks are welcome to contribute with all the other cloud storage offers :)
There was a problem hiding this comment.
Yes, I can look at doing that. Ideally I'd like to have it as the center piece of a "Running IPFS on AWS" piece. Having some basic templates and iam roles would be helpful for people I think.
daviddias
reviewed
Jan 29, 2019
| - Better custom lock example in datastore s3 [js-datastore-s3#13](https://github.com/ipfs/js-datastore-s3/pull/13) | ||
| - Also updated example for the latest js-ipfs | ||
| - Fix datastore s3 issue with multiple callbacks due to AWS lib [js-datastore-s3#14](https://github.com/ipfs/js-datastore-s3/pull/14) | ||
| - Now lead maintainer of js-multiaddr |
There was a problem hiding this comment.
Congratulations and thank you! ❤️
daviddias
reviewed
Jan 29, 2019
|
|
||
| @lidel | ||
| - Done: | ||
| - Quick update on Brave/Chromium: ipfs-companion extension ID is now whitelisted in Brave and we confirmed `chrome.sockets` API can be used to start HTTP server: [ipfs-companion/issues/664#comment](https://github.com/ipfs-shipyard/ipfs-companion/issues/664#issuecomment-458213687) (this is huge, as it confirms js-ipfs-in-webextension as a provider of HTTP Gateway is feasible \o/) |
There was a problem hiding this comment.
The world is completely missing on amazing this is. Let's write a script for a fun demoing while at FOSDEM that then we can record :)
daviddias
reviewed
Jan 29, 2019
| - Base protocol extracted from floodsub to its own module, to be used by gossipsub implementation | ||
| - @Mikerah from ChainSafeSystems will be implementing gossipsub for JS land | ||
| - Pubsub message benchmark | ||
| - [ipfs/benchmarks#210](https://github.com/ipfs/benchmarks/pull/210) |
daviddias
reviewed
Jan 29, 2019
|
|
||
| Done: | ||
| - DHT integration in `js-ipfs` | ||
| - CI is green now [ipfs/js-ipfs#856](https://github.com/ipfs/js-ipfs/pull/856) |
There was a problem hiding this comment.
Has this been tested across NATs? We should set a PoWoW Zoom Call where we go through multiple experiments and try to break it
There was a problem hiding this comment.
Currently, the only NAT traversal that we have is through circuit relay.
So, if we do a zoom and run local nodes, we should be able run findPeer successfully on each other id's. Then, we should be able to connect, at least over circuit relay. But yes, I agree that this would be a nice test to make!
daviddias
pushed a commit
that referenced
this pull request
Feb 5, 2019
* Create 2019-01-28--js-core-dev-team-weekly.md * Update 2019-01-28--js-core-dev-team-weekly.md
daviddias
added a commit
that referenced
this pull request
Feb 5, 2019
* docs: add badges * go and locol wg badges * docs: s/WG/Working Group/g * Update TEAM_STRUCTURES.md Co-Authored-By: daviddias <daviddias.p@gmail.com> * Create 2019-01-02--gui-and-in-web-browsers-weekly.md cc #790 * docs: add attendance, add link to libp2p-switch issue * IPFS Weekly Call Notes 2019-01-07 * Create 2019-01-07--go-core-dev-team-weekly.md * Added IPFS Weekly Call video * Add color to bigs update * Create 2019-01-09--gui-and-in-web-browsers-weekly.md License: MIT Signed-off-by: Marcin Rataj <lidel@lidel.org> * Add Community WG meeting notes for 2019-01-10 - Add IPFS Community Working Group Weekly Sync meeting notes for 2019-01-10 * docs: add Kanban resources * Create 2019-01-14--go-core-dev-team-weekly.md * January 14th 2018 IPFS Weekly Call * Add video links, edit Q&A notes - Added video links to the call recording and Teri's presentation - Edited/added Q&A notes * Create 2019-01-16--gui-and-in-web-browsers-weekly.md cc #790 * Create 2019-01-17--ipfs-community-wg-weekly.md - Add notes from 1/17 meeting of IFPS Community Working Group * Add IPFS Community WG Weekly Sync to list - Add Community WG to the list of working groups with weekly syncs. * Update 2019-01-14--ipfs-weekly-call.md Small formatting fixes * Create 2019-01-21--js-core-dev-team-weekly.md * Update 2019-01-21--js-core-dev-team-weekly.md * IPFS Weekly Call notes for 2019-21-1 * Create 2019-01-21--go-core-dev-team-weekly.md * Update 2019-01-21--go-core-dev-team-weekly.md * docs: update Weekly Calls format doc * fix: link to weekly call * Create 2019-01-23--gui-and-in-web-browsers-weekly.md cc #790 * Notes for the 2019-01-24 Community WG * Clarify a few details in meeting notes - Clarify a few details in meeting notes * Create 2019-01-28--go-core-dev-team-weekly.md * Notes for the IPFS Community Call 2019-1-28 (#854) * Notes for the IPFS Community Call 2019-1-28 * Added Youtube link next to video heading * Meeting notes for JS Core Dev 2019-01-14 (#837) * Create 2019-01-28--js-core-dev-team-weekly.md (#852) * Create 2019-01-28--js-core-dev-team-weekly.md * Update 2019-01-28--js-core-dev-team-weekly.md * IPFS Weekly Community Sync Notes 29.1 * docs: How to save a chat in zoom (#855) * Added how to save zoom call chats in faq * Minor formatting * Add 2019-01-30--gui-and-in-web-browsers-weekly.md (#856) * Add 2019-01-30--gui-and-in-web-browsers-weekly.md * Update 2019-01-30--gui-and-in-web-browsers-weekly.md * chore: apply suggestions from code review Co-Authored-By: fsdiogo <fsdiogo@gmail.com> * Create 2018-12-12-to-2019-01-15--cluster-meeting-archive.md (#840) * Create 2018-12-12-to-2019-01-15.md Standup notes * Rename 2018-12-12-to-2019-01-15.md to 2018-12-12-to-2019-01-15--cluster-meeting-archive.md * Create 2019-02-04--go-core-dev-team-weekly.md (#859) * docs: move badges to repo for simple updates
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.