Added 009! #34

RichardLitt · 2016-04-06T00:38:28Z

Needs review!

daviddias · 2016-04-06T01:11:02Z

published/009-2016-March-28.md

+
+@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


daviddias · 2016-04-06T01:15:41Z

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

hackergrrl · 2016-04-06T06:28:08Z

published/009-2016-March-28.md

+
+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.


s/daviddias/diasdavid (he's backwards on GH; forwards everywhere else)

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.

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.

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

ghost · 2016-04-06T16:25:30Z

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 · 2016-04-06T20:14:42Z

@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

daviddias · 2016-04-06T21:49:44Z

published/009-2016-March-28.md

+
+### Captain.log
+
+... TODO @diasdavid


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 · 2016-04-06T23:01:38Z

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

jbenet · 2016-04-19T00:57:43Z

published/009-2016-March-28.md

+
+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).


add after first sentence:

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

jbenet · 2016-04-19T01:14:12Z

published/009-2016-March-28.md

+
+### 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.


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

jbenet · 2016-04-20T01:30:08Z

published/009-2016-March-28.md


-@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)


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:

(or both. or a gif)

jbenet · 2016-04-20T01:30:56Z

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

First draft of IPFS Weekly #34

Added 009

7afec0c

RichardLitt added the needs review label Apr 6, 2016

daviddias reviewed Apr 6, 2016
View reviewed changes

hackergrrl reviewed Apr 6, 2016
View reviewed changes

Edits!

78cd2ca

Added more contribs, two stubs

22203d1

daviddias reviewed Apr 6, 2016
View reviewed changes

ghost mentioned this pull request Apr 12, 2016

Sprint: April 6 → April 18 ipfs/team-mgmt#101

Closed

RichardLitt added 4 commits April 12, 2016 17:13

Added Hyrdus

5cb7388

Added NYC Blockchain and event and MIT

4e24efb

Remove hydrus

e05b764

Added Christian photo

85a9326

jbenet reviewed Apr 19, 2016
View reviewed changes

RichardLitt added 2 commits April 19, 2016 16:06

Fixes from @jbenet

cf3484e

Final edits

8722dc9

jbenet reviewed Apr 20, 2016
View reviewed changes

daviddias removed the needs review label Apr 20, 2016

Update image

001414c

RichardLitt merged commit 0019d96 into master Apr 20, 2016

RichardLitt deleted the feature/9 branch April 20, 2016 17:55

jennwrites added a commit that referenced this pull request Mar 19, 2019

Merge pull request #84 from ipfs/ipfs-weekly-34

f9559c8

First draft of IPFS Weekly #34

jennwrites mentioned this pull request Mar 19, 2019

First draft of IPFS Weekly #34 #84

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added 009! #34

Added 009! #34

RichardLitt commented Apr 6, 2016

daviddias Apr 6, 2016

daviddias commented Apr 6, 2016

hackergrrl Apr 6, 2016

RichardLitt Apr 6, 2016

ghost commented Apr 6, 2016

RichardLitt commented Apr 6, 2016

daviddias Apr 6, 2016

nginnever commented Apr 6, 2016

jbenet Apr 19, 2016

jbenet Apr 19, 2016

jbenet Apr 20, 2016

jbenet Apr 20, 2016

jbenet commented Apr 20, 2016


		@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


		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.


		### 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.


		@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)

Added 009! #34

Added 009! #34

Conversation

RichardLitt commented Apr 6, 2016

Choose a reason for hiding this comment

daviddias commented Apr 6, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ghost commented Apr 6, 2016

RichardLitt commented Apr 6, 2016

Choose a reason for hiding this comment

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

nginnever commented Apr 6, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jbenet commented Apr 20, 2016