Init

published/011-2016-May-16.md

@@ -52,8 +52,16 @@ Orbit also got some love: @haadcode has been integrating the new orbit-db versio
 
 @RichardLitt made a spec for what a standard readme should look like, and plans to ensure that all IPFS repositories are up to that spec. He has also made a generator to help people create compliant readmes faster. This will help lessen the cognitive load involved with creating and maintaining READMEs. There are plans, in the works, to make a linter, too. If you think readmes are important, jump in with your opinions on the [spec](//github.com/RichardLitt/standard-readme)!
 
+### common-readme
+
 @noffle has also been working on readmes, by creating [common-readme](https://github.com/noffle/common-readme). This is more Node.js-specific than @RichardLitt's [standard-readme](//github.com/RichardLitt/standard-readme), and is aimed at making a standard way of presenting information for NPM modules. @noffle and @RichardLitt are going to spend more time working together and trying to make the best readmes they can.
 
+### [ipfs-twitter-resolver](https://github.com/noffle/ipfs-twitter-resolver)
+
+Finally, @noffle made an IPFS Twitter resolver: basically, a tiny CLI server for resolving `/twitter/user/key` to an IPFS address. It uses npm and ... (expect a blog post soon).
+
+TBD
+
 ## Community
 
 ### require('lx')