I'm curious to see how Wave fares under a python-dev-size debate, and what creative curating can accomplish. Sometimes I think the optimal solution to online d

I'm curious to see how Wave fares under a python-dev-size debate, and what creative curating can accomplish. Sometimes I think the optimal solution to online discussion is a reconfigurable 3d visualization of the graph of comment-nodes. In one configuration, node size, location, connectedness and proximity to the core of the graph would signify a comment's relative importance and "page-rank". The ability to respond to and "link" to multiple other comments would be useful here. Another would be a more standard tree-based visualization of the comments in time, but without the misleading vertical ranking of root nodes. Another visualization might be a straight serialization in time, similar to mailing lists. I imagine the nodes to be sort of bouncy, physicsy bubbles that can be nudged around, and that the view can rotate in three dimensions and zoom in and out to focus on specific subthreads. Other times I think that's way too heavy-weight a solution, that it would be confusing, that it might not actually solve anything, and that we do pretty well with the threaded comment trees we have now. I actually kind like that everyone sees the same thing on the page, shared experience and whatnot. I dunno. Online discussion is hard.