tsgates

Thanks for sharing the work.

Tl;dr. autofz is a meta fuzzer that combines a group of fuzzers and outperforms each of individual fuzzers. Since each fuzzer shows completely different characteristics for each targets, it was cumbersome for developers to determine which fuzzer to adopt and to evaluate them for best fit. With autofz, it simply figures out -- based on past execution behavior and responses of each fuzzer, at runtime, and allocates the proper resource to maximize the output (i.e., bug finding and code coverage) of the fuzzing process.

"just" is not a fair term. check its detail. we have designed VM, Multicore and Networking stack based on Rust 2018.

A "big" difference is that we have VM, Multicore and Networking stack! Also, it uses Rust 2018.

B2BWiki is a project that attempts to help Wikipedia in reducing down its network burden by delivering and sharing the page content among users by using in-browser P2P (WebRTC). Each user can contribute his/her network capacity as well as own local storage (e.g., localDB) in browser while reading the page, and a larger organization might even contribute to the community by deploying own servers (no out-of-pocket money!), similar to a mirroring server in an old good day.

I am the author of mbox. Since I got too many emails regarding mbox, here are a few things to clarify.

  - naming: pkgfile mbox || echo looks like a good name
  - support: sorry, I don't have Mac or Windows.

I particularly like to use mbox for redirecting modification to another directory. For example,

  $ mbox -- git checkout file

You can checkout a file without overwritting the current file. You can imagine tons of usecases in this vein. Of course, blocking networks, restricting accesses of other directories, and rootless pkg installations are cute. However, to be a mature tool, I have to admit that there are lots of engineering works left -- support of 32bit .. compatibility layers .. still lots of corner cases.