Welcome to the first edition of IPFS Weekly!
IPFS is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we will try to highlight some of the development that 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 (#ipfs on the Freenode network).
Since this is our first time launching the Weekly, we've included several past weeks. This is partially because we've been refining our process, and wanted to make the first weekly a great one. In the future, they will be released weekly. If you have any feedback about this process in general, let us know here. Thanks!
# December 21
Here are some of the highlights for the December 21 Sprint:
# 32c3
Not too much happened during this sprint, because it was the holidays - however, it was also the 32nd CCC. @whyrusleeping, @diasdavid, @lgierth, @Dignifiedquire and more of the team were over there in Hamburg.
- @whyrusleeping gave a lightning talk (see above).
- @whyrusleeping @diasdavid and @Dignifiedquire led an install party and live demo.
- @MrChrisJ led a discussion about his Full Node project, which includes IPFS.
- We met lots of our users, and other groups (including Tahoe-LAFS (opens new window), tor (opens new window), etc).
# Updates
- (go-ipfs) @whyrusleeping and @diasdavid did amazing work closing around 200 issues as part of the "Great go-ipfs Issue Party of 2015".
- (registry-mirror) npm on IPFS was furthered by @diasdavid by making it work with 0.4.0. Currently, there are 130,000 modules and it's going strong.
- (go-ipfs) @lgierth set up namaka and hiiaka (NUC nodes at our table at 32c3). This is pretty cool. CF. ipfs/infrastructure#142.
- (readme-standard) @RichardLitt had his own great issue party. He's most proud of breaking ground on the future readme standard for IPFS.
- (webui) @Dignifiedquire did some awesome work improving the webui using webpack.
- He also managed to release rust-multiaddr and rust-multihash, which means more languages now implement the orginal multihash and multiaddr specs.
For more updates, see the sprint issue.
# December 14
Here are some of the highlights for the December 14 Sprint:
# Releases
- @whyrusleeping shipped fs-repo-migrations! These are migrations for the filesystem repository of ipfs clients. This tool is written in Go, and developed alongside go-ipfs, but it should work with any repo conforming to the fs-repo specs.
- @Dignifiedquire did some great work with rust-multiaddr, which is a Rust implementation of @jbenet's multiaddr.
# Updates
- (registry-mirror) @diasdavid worked on the npm on IPFS project. This involved some new features, moving the mirror to a different server, and making it work better with larger dirs and with 0.4.0.
- (js-ipfs) @diasdavid pushed some major updates for js-ipfs, too.
Not much else to report this week; a lot of people are off to enjoy CCC, and the holidays.
# December 7th
Here are some highlights of what happened during the December 7 Sprint :
# Releases
- @whyrusleeping shipped IPFS version 0.3.10! It contains 74 new commits since the previous version and you can get it here.
- npm on IPFS!
registry-mirroris a new tool that enables distributed discovery of npm modules by fetching and caching the latest state of npm through IPNS. For more info, see this blog post by @diasdavid . - @jbenet released a new tool/library called dnslink that makes it easy to resolve dns links (special TXT records in a domain name that can point to paths, like an IPFS path)
# Updates
- (infrastructure) On the infrastructure side of things, @lgierth has bootstrapped two new storage, each with 17 TB of disk space!
- (api) @RichardLitt has [reached a draft 1]((//github.com/ipfs/api/pull/13) of the much needed API documentation.
- @harlantwood wrote a bit of nodejs code that spins up a fresh IPFS node, sets it to a known ID, and publishes to IPNS using that node.
- (specs) The new IPFS Linked Data (IPLD) spec is actively being iterated on in the specs repository. Join the discussion here!
# Active stuff
- @robcat and @fazo96 have done great work integrating IPFS with pacman (the package manager for Arch Linux). They can now install arch packages straight from IPFS! For more details, see this active discussion.
- @Dignifiedquire has been working on an attractive new distribution page for IPFS, which will be the new landing page to download all things IPFS. You can see the latest screenshots here.
# Contributors
Across the entire IPFS GitHub organization, the following people have committed code since December 7th. (We're autogenerating this list using this tool, so please let us know if your name isn't here.) In the future, we will also include people who comment, as they are also super important; bear with us while we develop that technology.
- @alexmingoia (Alex Mingoia)
- @chriscool (Christian Couder)
- @diasdavid (David Dias)
- @digital-dreamer
- @Dignifiedquire (Friedel Ziegelmayer)
- @djdv (Dominic Della Valle)
- @fazo96 (Enrico Fasoli)
- @greenkeeperio-bot
- @harlantwood (Harlan T Wood)
- @hcs64 (Adam Gashlin)
- @ianopolous (Ian Preston)
- @ivilata (Ivan Vilata-i-Balaguer)
- @jbenet (Juan Benet)
- @jedahan (Jonathan Dahan)
- @Kubuxu (Jakub Sztandera)
- @kyledrake (Kyle Drake)
- @lgierth (Lars Gierth)
- @NeoTeo (Teo Sartori)
- @ralphtheninja (Lars-Magnus Skog)
- @ReadmeCritic
- @rht
- @RichardLitt (Richard Littauer)
- @travisperson (Travis Person)
- @wasserfuhr (RainerWasserfuhr)
- @whyrusleeping (Jeromy Johnson)
- @zignig (Simon Kirkby)
Thanks, and see you next week!
- Richard Littauer and Andrew Chin