Der Management aren't exactly swamped by submissions, so why not view the queue? Guys?

Now if Foresight is so keen on open development and hyperlinking yada yada, would it not make sense to do as Rob says and at least try to have a common anydot entry point? Before Newsforge or Atomasoft gets the better of it all?

Atomasoft is already the most up-to-date place to get free nanotech news. Some may have had their disagreements with the site's editor, but he seems to be trying hard enough. If he puts up some feedback forum support and manages to keep his own opinions out of it, nanodot could be in for a rough ride.

Vik :v)

The nice part of this is the way the copper dislocation is used as a kind of welding trough to hold the workpiece against.

Now, if we can roll the workpiece around somehow, we might just be able to build in three dimensions while only having to move our tools in two.

Vik :v)

I noticed this on the 25th when it came out and thought it was very cool. Particularly since the work is coming out of Germany. The implications are nice because it confirms earlier work by Lee and Ho at Cornell [ Science 286(5445):1719-22 (26 Nov 1999)] that STM-tip chemistry is feasible. It is going to become increasingly difficult for the serious scientists to ignore this.

I posted three comments to the Slashdot discussion here. I did not post it to Nanodot however because the management have dictated we cannot view the pending submissions queue (when Nanodot first came up you could view the queue when you went to submit a story). For those who think your time is valuable enough to not want to waste time filing submissions that have already been filed (its like newspapers sending multiple reporters to cover the same story from the same angle), I'd urge you to send a note to the management requesting that they alter this policy. I don't see how you can want Open Source, but Closed Reporting. If people don't like this, we can always start OpenNanodot.org where you can view the submissions queue!

People aren't going to post comments to one XXXdot and then go repost them to another XXXdot. A means of creating metaXXXdot discussions needs to be found. I tried pointing this out to the authors of the /. code a year ago but they don't seem to have put a solution very high on the priority list. Sigh. Maybe now that we have /. and Nanodot and Extrodot, we can expect this problem to crop up increasingly, so perhaps it will get more attention.