Here's how you create a Soylent without losing the DIY aesthetic: 1) You make it an open source project under an open license, OpenSoylent 2) You leave any he

Here's how you create a Soylent without losing the DIY aesthetic: 1) You make it an open source project under an open license, OpenSoylent 2) You leave any health claims to be made by the OpenSoylent community. If this is unsatisfactory, you put out a bounty for MetaMed to write an independent report on the OpenSoylent wiki with references. 3) You accept people's patches to OpenSoylent 4) You create a separate, unaffilliated company to provide Soylent(tm), an implementation of OpenSoylent, with zero health claims, in a commercial kitchen, and link back to the OpenSoylent wiki for more information Whether the above is legal or not, I'm not certain, but A) it's a hell of a lot closer than the present situation, and B) it doesn't offend geeks who apply critical thought to businesses that blog.