I believe the question you wanted to ask was more along the lines of compatibility or openness. Leave that nasty S-word out of it, and you'd likely have gotten much less laughter.
Lactic acid is in your muscles right now. Acetic acid is vinegar minus some nutrients. Peroxyacetic acid breaks down into acetic acid and hydrogen peroxide.
Doesn't sound like dangerous chemicals to me. Heck, rinsing with plain old vinegar would be at least twice as acidic. (plus whatever else is in vinegar besides acetic acid.)
I'm with grandparent wondering about what these terrible chemicals are. If the issue is that chemicals have to be used at all, industrialized food production isn't going to disappear, and does have things to recommend it. (in the way of safety and scalability, which is important as populations will continue to rise in the foreseeable future)
I would much rather have meat I'll eat sprayed with some vinegar to kill off bacteria than go through a night of dehydration and vomiting with an IV in my arm at the hospital. (never order chicken strips first thing in the morning at a fast food restaurant.)
I know it is all supposed to be open source and everything but there is no Client-server protocol because it is assumed to be a web application so for a long time all we will have is Google's bloated JavaShit-filled and presumably ad-laden perpetual beta web interface.
And what about delayed-send messages? What if your reception at [place] is horrible, and you sent a text before getting in the car?
The goal was to replace email. The result is a cross between email, threaded discussion, wiki, and instant messaging. (no, really. Live concurrent collaborative editing, along with a rewind feature so you can review the chronology in a more logical fashion) One can make gadgets that show up in a wave and allow you to interact in ways besides just typing, and there are also bots that interact with waves much like a normal user. Instead of adding some spell check the way you might normally think of it, they have a spell check bot that uses the wave collaborative editing features to highlight and potentially change your spelling. (which means someone else in the conversation could finish up doing the editing the spell check highlighted in a sentence earlier in your paragraph)
It works somewhat like email, as in once things settle down whoever can run their own wave server. And it could be integrated with, say, a blog where the comment section of a post would be a wave. (and have all that functionality, and stuff)