{"componentChunkName":"component---src-templates-page-js","path":"/notes/tagteam-work-in-progress","result":{"data":{"markdownRemark":{"html":"<p><img src=\"/img/uploads/2011/01/tagteam.jpg\" alt=\"A screenshot of the Tag Team interface, showing a drawing component on the left and a writing component on the right\"></p>\n<p>What started off as the <a href=\"/notes/beginning-node-js-and-socket-io/\">world's dumbest chatroom</a> a few weeks ago is gradually turning into something cooler. \"Tag Team,\" as I’m calling it (for now), lets a writer and a drawer collaborate on whatever they would like. I’ve put my updated source on <a href=\"https://github.com/sambrenner/tagteam\">GitHub</a> so you can play around with it yourself. Here are some next steps:</p>\n<ul>\n<li>Design the site and user experience – tasked to my <a href=\"http://ameliahall.com/\">co-conspirator</a></li>\n<li>Get it up online – <a href=\"https://web.archive.org/web/20110124224232/http://nodester.com/\">nodester</a> looks like a good starting point</li>\n<li>Optimization – in particular, with how the image is transmitted. Currently I’m encoding the canvas as a png using `canvas.toDataURL()` and sending that over the server, which is a little laggy. I might try seeing only what parts of the encoded string have changed and send that instead.</li>\n<li>Security – still really easy to send whatever instructions you want to the server.</li>\n</ul>","frontmatter":{"path":"/notes/tagteam-work-in-progress","title":"Tag Team work in progress","date":"2011-01-19T04:08:58.000Z","categories":["Node.js","JavaScript","Experiments"],"churl":null,"uses":null}}},"pageContext":{"post":true,"prev":{"url":"/notes/beginning-node-js-and-socket-io","title":"Beginning node.js and socket.io"},"next":{"url":"/notes/back-to-the-blog/","title":"Back to the blog"}}}}