You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: published/008-2016-March-21.md
+82-6Lines changed: 82 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -8,24 +8,100 @@ Here are some of the highlights for the [March 14](//github.com/ipfs/pm/issues/9
8
8
9
9
## Updates
10
10
11
-
*[**__Repo__**](//github.com/)
11
+
### PubSub
12
12
13
-
## Work in Progress
13
+
There are some active discussions on PubSub, following a good video chat last week during the hangouts. PubSub is the name we're using to talk about a simple protocol which will help facilitate easy publishing and subscribing on top of IPFS. Our requirements are that it must be easy to implement, well-layered, and mesh well with the rest of the IPFS abstractions. To join the conversation about the PubSub API, check out this [issue](https://github.com/ipfs/notes/issues/118). For more discussions, check out all of the [PubSub issues in the notes repo](https://github.com/ipfs/notes/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pubsub).
[@haadcode](//github.com/haadcode) has been working on and released [ipfs-log](https://github.com/haadcode/ipfs-log), a partially ordered linked list of IPFS hashes. Each entry in the log points to all known heads or leaf nodes. It can be used as a building block for applications that need to track "dynamic content", eg. track a version of a file, create a feed of IPFS hashes, messaging or as a transport for CRDTs. THis was originally created for, and is currently used in, [orbit-db](https://github.com/haadcode/orbit-db), a KV-store and Event Log on IPFS.
18
+
19
+
### ipfs init
20
+
21
+
`ipfs init` for js-ipfs [is almost complete](https://github.com/ipfs/js-ipfs/pull/91), thanks to [@noffle](//github.com/noffle). This will have go-ipfs compatibility, but run using only JavaScript. If you like building tests and sharpening your semicolons, there's plenty of [opportunities to contribute](https://github.com/ipfs/js-ipfs#contribute) in js-ipfs land.
15
22
16
23
## Community
17
24
25
+
### Lisbon
18
26
19
-
## Contributors
27
+
[@diasdavid](//github.com/diasdavid) organized a research and development meeting for IPFS in Lisbon. If you're in the area, join [this meetup group](http://www.meetup.com/ipfs-lisbon-meetup/events/229530492/).
20
28
21
-
Across the entire IPFS GitHub organization, the following people have committed code, created issues, or made a comment on GitHub between __Date__ (noon, GMT) and __Date__. We're autogenerating this list using [this tool](//github.com/ipfs/weekly/blob/master/tools/get_commits.py) and [this other tool](//github.com/richardlitt/name-your-contributors), so please let us know if your name isn't here.
29
+
## Press
30
+
31
+
Bitcoin Magazine had a guest post by [Zach Ramsay](https://twitter.com/cerebralbosons), from Eris Industries, about [How Blockchains Can Further Public Science](http://www.nasdaq.com/article/how-blockchains-can-further-public-science-cm592775). Zach also published part two on the Eris blog: [Public Science: A Slightly More Practical Guide](https://db.erisindustries.com/science/2016/03/15/chains-and-science-how-to/). Both are well worth the read, especially if you're in academia.
32
+
33
+
## Contributors
22
34
23
-
-__Contributors__
35
+
Across the entire IPFS GitHub organization, the following people have committed code, created issues, or made a comment on GitHub between March 14th (noon, GMT) and March 21st. We're autogenerating this list using [this tool](//github.com/ipfs/weekly/blob/master/tools/get_commits.py) and [this other tool](//github.com/richardlitt/name-your-contributors), so please let us know if your name isn't here.
This newsletter is also a community effort. If you have cool things to share for the next weekly, drop a comment about it in the [next weekly sprint issue](__TODO__)! The more people mention items they want to see in the weekly there, the easier it is to make this and send it out.
26
102
27
103
Thanks, and see you next week!
28
104
29
105
- Richard Littauer
30
106
31
-
_Submit feedback about this issue [here](__TODO__), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
107
+
_Submit feedback about this issue [here](//github.com/ipfs/weekly/issues/29), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
0 commit comments