IPFS is a , by and , aiming to make the web faster, safer, and more open. In these posts, we highlight some of the development that has happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on GitHub or join us on IRC (# on the Freenode network).
If you would like to get this update as an email, sign up for our weekly newsletter!
Here are some of the highlights for the March 14 sprint:
@dignifiedquire has been working hard on the new webui, which will be coming soon. You’ll be able to preview images, watch videos, create folders, drag and drop, and more. Here’s a pretty gif. To help out, check out the help wanted labels on the repo.
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 issue. For more discussions, check out all of the PubSub issues in the notes repo.. 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
@haadcode has been working on and released 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, a KV-store and Event Log on IPFS.
This week in go-ipfs, we prepped for shipping version 0.4.0. This included lots of testing, writing of information, and verification of different aspects of IPFS. @whyrusleeping wrote a stress test for the fs-repo-migrations that adds a very large number of objects (over 200,000) and pins a couple thousand of them, runs the migration, verifies everything, runs a gc, and then verifies everything again. Once that got working, he kicked off a test run of that with the numbers bumped by a factor of 10 (over two million objects!) and everything completed just fine. This robustness means that 0.4.0 will be ready to ship very, very soon.
There were some changes in ipfs-firefox-addon since it was mentioned in Weekly No.3 (v1.4.2).
The 1.5.x series brings various UX improvements such as Realtime Status and Diagnostics, along with experimental features that can be enabled on the Preferences screen. Check the full list at Github. Feature requests and bug reports are welcome!
Our friends at Mine recently released L-SPACE, the Mediachain server. they have also been writing great updates to their blog: How Mediachain works, Dev Update V, Dev Update VI, and more. The press took notice and Mediachain has been featured in Nasdaq, Bitcoin Magazine, CCN, and more! Congratulations, and thanks for the IPFS shoutouts there!
Bitcoin Magazine had a guest post by Zach Ramsay, from Eris Industries, about How Blockchains Can Further Public Science. Zach also published part two on the Eris blog: Public Science: A Slightly More Practical Guide. Both are well worth the read, especially if you’re in academia.
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 and this other tool, so please let us know if your name isn’t here.
- @amstocker (Andrew Stocker)
- @anarcat (anarcat)
- @ansuz (ansuz)
- @basile-henry (Basile Henry)
- @bdunlay (Brian Dunlay)
- @brainframe-me (Cox Davy)
- @candeira (Javier Candeira)
- @chriscool (Christian Couder)
- @christianlundkvist (Christian Lundkvist)
- @clkao (Chia-liang Kao)
- @davidar (David A Roberts)
- @diasdavid (David Dias)
- @dignifiedquire (Friedel Ziegelmayer)
- @doesntgolf (Nate Dobbins)
- @ehd (Stephan Seidt)
- @eminence (Andrew Chin)
- @fazo96 (Enrico Fasoli)
- @GoogilyBoogily (Derek Mayer)
- @greenkeeperio-bot (Greenkeeper)
- @haadcode (Haad)
- @harlantwood (Harlan T Wood)
- @ianopolous (Ian Preston)
- @ingokeck (Ingo Keck)
- @jbenet (Juan Benet)
- @jwsher (Justin Sher)
- @kalmi (Tarnay Kálmán)
- @kevina (Kevin Atkinson)
- @kseistrup (Klaus Alexander Seistrup)
- @Kubuxu (Jakub Sztandera)
- @lgierth (Lars Gierth)
- @lidel (Marcin Rataj)
- @luigiplr (Luigi Poole)
- @matshenricson (Mats Henricson)
- @Mec-iS (Lorenzo)
- @mildred (Mildred Ki’Lya)
- @mnp (Mitchell Perilstein)
- @nginnever (Nathan Ginnever)
- @nicola (Nicola Greco)
- @noffle (Stephen Whitmore)
- @palkeo (palkeo)
- @RichardLitt (Richard Littauer)
- @sahib (Chris Pahl)
- @se3000 (Steve Ellis)
- @sexybiggetje (Martijn de Boer)
- @sivachandran (Sivachandran)
- @Stebalien (Steven Allen)
- @thelinuxkid (Andres Buritica)
- @wasserfuhr (RainerWasserfuhr)
- @whyrusleeping (Jeromy Johnson)
- @willglynn (Will Glynn)
- @wking (W. Trevor King)
- @xicombd (Francisco Baio Dias)
This newsletter is also a community effort. If you have cool things to share for the next next weekly sprint issue! The more people mention items they want to see in the weekly there, the easier it is to make this and send it out., drop a comment about it in the
Thanks, and see you next week!
- Richard Littauer