Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added 009! #34

Merged
merged 10 commits into from
Apr 20, 2016
Merged

Added 009! #34

merged 10 commits into from
Apr 20, 2016

Conversation

RichardLitt
Copy link
Member

Needs review!


@jbenet and @lgierth met with the fine folks of [nycmesh.net](https://nycmesh.net). For the past two years they've been building a community Wifi network in New York City. We had lots of great conversation about wireless mesh networking and IPFS. If you live in NYC, you should come attend their [meetups](http://www.meetup.com/nycmesh/)!

### Lisbon Research and Development
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Meetup

@daviddias
Copy link
Member

Could you (pretty please) add an extra section about the latest captain.log entry? ipfs/js-ipfs#30 (comment)


Many people jumped to IPFS as a possible solution to this problem. With a permanent filesystem, unpublishing wouldn't be possible. Here's one post titled [How to use IPFS to fix npm](http://amreldib.com/blog/HowToUseIpfsToFixNpm); here's [an issue](https://github.com/ipmjs/ipmjs/issues/9) on a new GitHub organization, ipmjs, trying to find consensus on how to fix npm using a permanent storage system; here's an npm module, [cowpen](https://www.npmjs.com/package/cowpen) that publishes modules directly to IPFS; here's [another decentralized package manager](https://github.com/mhhf/spore) that sprung up using IPFS and Ethereum.

The IPFS community has been thinking about immutable package managers for a long time. @daviddias has a project called `registry-mirror`, which gets npm packages by using IPFS. He's written about a presentation he gave for it, [here](http://blog.daviddias.me/2015/12/08/stellar-module-management); the [source code](https://github.com/diasdavid/registry-mirror) is here.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. s/daviddias/diasdavid (he's backwards on GH; forwards everywhere else)
  2. If you don't me suggesting: "[...] registry-mirror, which allows you to run an npm registry locally that is backed by packages retrieved from IPFS instead of NPM directly." for more conciseness on what it does.
  3. Nitpick: maybe linkify "here" instead of "source code"? I'm being english-y nitpick-y here and wouldn't do it if it wasn't you @RichardLitt ❤️ -- but I think the nomenclature of using "here" in online documents only works because the noun refers to the hyperlink that it is contained within. Please feel free to disagree -- Strunk and White very well might.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gah I hate Strunk and white. But yeah, changed.

@ghost
Copy link

ghost commented Apr 6, 2016

Great weekly! Typed a few words for the new section "Content-Type of the Week"

## Content-Type of the Week

Now that we're using mtail to make better sense of nginx serving the
IPFS-to-HTTP gateway, we can graph the frequency of content types served.
We'll showcase interesting content types served from the gateway in the coming
weeklies.

The first Content-Type of the week is: application/x-chdr, which signifies a C source header file.

@RichardLitt
Copy link
Member Author

@noffle @lgierth @haadcode @diasdavid @whyrusleeping @nginnever @jbenet @eminence Going to be changing this to a double-issue; also going to be doing last week. This is 100% my bad. Can you add anything here or in the collection issue for everything before this Monday?

Things I need to add:

  • Wednesday Event at AWS


### Captain.log

... TODO @diasdavid
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aye, you might want to check the new js-ipfs Captain.log entry, mate!

Following js-ipfs roadmap, we’re close™ to have a workable js-ipfs version that can be used in the browser and in Node.js. This will mark a very important milestone on the IPFS project and enable a whole set of new distributed web applications to be possible. If you want to be part of this effort, check out our Captain.log entry to get a full update and a list of tasks you can contribute to.

@nginnever
Copy link
Member

This Monday members of the IPFS comminuty attended a blockchain workshop event held by Coala, "a collaboration between academics, lawyers, technologists and entrepreneurs who have been driving research, policy and infrastructure-building in the blockchain ecosystem for the past three years" at the New York University School of Business. @diasdavid @haad @noffle and @nginnever were in attendance as @jbenet was a part of a protocols panel, speaking on scalability and the future of blockchain technology. A recording of the event should be available on youtube in the future at the following youtube channel link https://www.youtube.com/channel/UC9Lmf5FfNkSmYMoxhQh5ktA


Many people jumped to IPFS as a possible solution to this problem. With a permanent filesystem, unpublishing wouldn't be possible. Here's one post titled [How to use IPFS to fix npm](http://amreldib.com/blog/HowToUseIpfsToFixNpm); here's [an issue](https://github.com/ipmjs/ipmjs/issues/9) on a new GitHub organization, ipmjs, trying to find consensus on how to fix npm using a permanent storage system; here's an npm module, [cowpen](https://www.npmjs.com/package/cowpen) that publishes modules directly to IPFS; here's [another decentralized package manager](https://github.com/mhhf/spore) that sprung up using IPFS and Ethereum.

The IPFS community has been thinking about immutable package managers for a long time. @diasdavid has a project called `registry-mirror`, which allows you to run an npm registry locally that is backed by packages retrieved from IPFS instead of NPM directly. He's written about a presentation he gave for it, [here](http://blog.daviddias.me/2015/12/08/stellar-module-management); the source code is [here](https://github.com/diasdavid/registry-mirror).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add after first sentence:

IPFS itself began as an immutable package manager, and it is built to make writing them much easier.


### Orbit

@haadcode has been working on improvements to [orbit-db](https://github.com/haadcode/orbit-db), [ipfs-log](https://github.com/haadcode/ipfs-log/) and [Orbit](https://github.com/haadcode/orbit). The message history fetching is now more stable and the UI feedback for loading messages is fixed. All this work will improve the user experience of Orbit.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orbit is a huge deal, grab a screenshot from its readme


@haadcode has been working on improvements to [orbit-db](https://github.com/haadcode/orbit-db), [ipfs-log](https://github.com/haadcode/ipfs-log/) and [Orbit](https://github.com/haadcode/orbit). The message history fetching is now more stable and the UI feedback for loading messages is fixed. All this work will improve the user experience of Orbit.
![Orbit](009_orbit.png)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image of orbit does not highlight the main point of orbit: realtime chat. It's mostly hidden by the side bar. How about this one instead:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(or both. or a gif)

@jbenet
Copy link
Member

jbenet commented Apr 20, 2016

thanks for the changes. image fix needed only, and LGTM to ship

@RichardLitt RichardLitt merged commit 0019d96 into master Apr 20, 2016
@RichardLitt RichardLitt deleted the feature/9 branch April 20, 2016 17:55
jennwrites added a commit that referenced this pull request Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants