Under the intense field the protons are going to oscillate back and forth under the optical electric field - note, the electrons will do this even more, as they are ~ 1/2000 as massive. With a beam, you only interact once, here the protons may interact for the lifetime of the pulse - which is very short. The question is the fusion yield vs the energy needed to drive the field. Muon catalyzed fusion worked very well - but the cost to create the muons was too high.

I ran across some music I was looking for behind a "warning, dangerous and offensive" material warning a few weeks ago. I was looking for a Ukrainian nationalist song - my translation is 'Kalina in the Valley' from one of the historical Ukrainian nationalist groups. Yes, the song was sung by a group that collaborated with the Germans in WW2. And singing or humming it during the Soviet era would get you a one-way ticked to Siberia. Doing so now in Russia would result in the same fate. There may be a broad brush here. Simply banning material does not address the issues.

I have been expecting this for a while. The real question I have had is how they would implement the feedback weights. You can do it with switches and a bank or resistors, but a memristor as a feedback element would be much more efficient - and should be far denser.

Actually, the plug-in hybrids aren't likely to age out so fast. I had to replace my old Forrester. I got a Prius Prime, which gets > 25 miles on electric, handling most of my commuting. It then gets over 50 mpg on gas, making it well suited to long range driving - I will do well over 1000 miles a day when on the road. I bought it, not leased it. I figure in another 4 years I will replace my wife's Corolla with an all electric self-driving vehicle, as she is directionally challenged.

I have been using Brother workgroup printers for years. I will go long times without printing, and then print 60 page double sided docs. The printers are relatively cheap - and fast. And they are cheap to run. My current version eats full reams of paper. Even the Brother cartridges work out to about $.01 per side of print, and the no-name cartridges are far cheaper.

I have seen the mess of cables necessary to support electric trolleys in Seattle and elsewhere. With batteries, you could reduce the overhead wiring to straight streets and above bus stops,where it is cheap to install and power, allowing charging during normal operation. At stops, the bus stops for a while to take on and let off passengers, and buses have stops for a few minutes at the beginning and end of routs at terminals to allow the drivers to get up and use the facilities. All are good opportunities for high rate charging.

Systems submitted for evaluation under TCSEC B2 and better had to be designed for security - layering, TCB minimization, ... were all mandated in addition to support for trusted MAC functionality. When I am designing for "SECURITY" I want to simplify the critical protocols so that they can be described by a state machine and then implement them in silicon.

I don't know. I am not involved with this. Clearly, the Air Force, or other customer can define what security policy they want to apply and have their systems configured to it.

I am a security program manager at Microsoft. The article gets much of it wrong. The Air Force wanted the machines preconfigured to a secure configuration so that they did not have to do this configuration. Such configurations are not distributed to the general public because of the impact on generalized consumer useability. Microsoft always publishes a security guide which provides guidance on configuring systems for different threat environments. For example in the Windows Vista Security Guide, Chapter 5 is titled "Specialized Security - Limited Functionality". Such security guides exist for NT on.

Users are free to configure their systems for higher security. Note that doing so may limit functionality you are used to. For example, you can configure your system so that all users run as normal users (no administrative functionality). Running users as normal users is part of all security guidance. Not all XP software will run if you do this. You can set IE to high security mode by default and disable Flash, etc. Doing so breaks much of the web but is more secure. You can get security, but it will impact your user experience.

It is easier to secure Vista and 2K8 server systems.

While the near-shore environment is reasonably suited to cables, the cost of long distance power transmission in the deep ocean environment may be problematic. This suggests that the power be stored into some transmissible fuel that can be picked up intermittently. One possibility would be Ammonia, NH3, which could be made by electrolysis of water to get the Hydrogen and nitrogen from the atmosphere. The heat of formation of NH3 is ~ 10% of the available energy in the Hydrogen (liquefying Hydrogen requires ~ 30%). Anhydrous ammonia is easily handled at moderate pressures in steel vessels, has a higher volumetric density than liquid Hydrogen, could be easily handled by tankers, and the Hydrogen can be easily released at moderate temperatures by catalytic reforming. Spills of NH3 are limited by its high solubility in water and lack of persistence - plants metabolize it rapidly.

The theory is quite strong in this case. As for the virtual electron and positron meeting and anhilating each other, that is what they do all the time all over the universe - look up a good introduction to quantum field theory, which is very well supported by experimental tests.

We have no evidence for black holes of less than multiples of the sun's mass and to the best of my knowledge, no evidence of black holes of masses on the order of many billions of solar masses. The rest is speculation, but not unreasonable.

There was a very interesting paper at the LANL archives last year on the energy release from small black holes on planetary bodies due to eddington-limited accretion. The impact would be correspondingly greater and more observable in white dwarfs and neutron stars.

Small black holes are far less dangerous than made out to be. I wouldn't like to be very near one due to its Hawking radiation (virtual photon creation near the event horizon where one of the virtual photons is absorbed and the other turns real as it escapes), but the fear mongers of black holes forget the limiting factor. Matter falling into a black hole is compressed and gets hot. The hot matter radiates light / gamma rays. While in some cases this radiation might be captured as well, it is far more likely that the radiation pressure will limit the rate of matter absorption by the black hole. The radiation pressure effect is known as the Eddinton effect and is a major factor in stellar stability. In the case of a small black hole, the size of the black hole is far smaller than the absorption length of gamma rays, preventing advection of the gammas. Since a non-rotating black hole is likely to convert on the order of 1% of the absorbed mass into gamma radiation, such a source would be more than capable of creating a near vacuum of hot matter about itself.

If such stable black holes were creatable / existed, we should see rather remarkable things with old white dwarfs and neutron stars, which would be greatly affected by such energy sources.

Strong passwords / keys for WPA is not much of a burden. You only have to enter the damm things once. I use a random 32 character hex string as my key. I wrote it down and stored it in a known location. I also have it stored in an old USB drive in a text file. I have to enter it far more than most people, as I dogfood WIndows releases, flattening my notebook each time. Thus I have to reinitialize it for my home WPA network each time I rebuild it. I am not worrying about brute force attacks against 128 bit key values.

Actually, it is rather more like the Zotob vuln than the Blaster vuln. It is a crit on earlier systems, but requires authenticated privledges on Vista and 2K8 server due to the implementation of the integrity level defenses in Vista and 2K8. That said, the potential for damage with this vulnerability is high and there were reports of attacks in the wild. Thus, Microsoft released out of the standard release cycle.