LiftrTM – A Web 2.0 Name for a Nuclear 4.1 Technology

ByRod Adams

Now that I have had a chance to view the Google Tech Talk I embedded in my post yesterday evening, I am inspired to make a few suggestions to the loose group of people that are working on Liquid Fluoride Thorium Reactors.

  • Change the name from LFTR, a bureaucratic looking acronym to LiftrTM – a modern looking word that is easy to pronounce.
  • Recognize that this is evolving as an “open source” reactor project.
  • Establish a non-profit foundation similar to Mozilla that can establish the necessary infrastructure.
  • Continue efforts to educate and promote, but bring in some business people to focus resources.
  • Build a support base of people who understand technology and how to use it to disturb long standing markets.
  • Get the ear and pocketbook of key innovators. Suggested names (you can add to the call list via comments) – Jason Calacanis, Leo LaPorte, Mark Cuban, Adam Curry, Aubrey McClendon, Regis Matzie, Linden Blue and David Crane
  • Start all of the above yesterday.

If you have not already watched the Liquid Fluoride Thorium Reactor talk that Dr. Joe Bonometti gave as a Google Tech Talk, do so. If you want to learn more about the technology, go to Energy from Thorium. If you are ready to join the open source reactor project, sign up for the Energy from Thorium Forum.

PS – Just a word about the blog title – I know that “Web 2.0” is a huge buzz word, but I have never figured out why people get so excited about the “.0” part. I know that is where all of the big breakthroughs occur, but I personally avoid all “.0” versions of software. I prefer the refinements and bug fixes that come in the “.1”, “.2” and “.15” releases. One of the reasons I am such a big fission fan is that we have now gained 50 years of knowledge and operating experience from the “.0” generation. We know how to improve on an already excellent product.

Rod Adams
Rod Adams

Rod Adams is Managing Partner of Nucleation Capital, a venture fund that invests in advanced nuclear, which provides affordable access to this clean energy sector to pronuclear and impact investors. Rod, a former submarine Engineer Officer and founder of Adams Atomic Engines, Inc., which was one of the earliest advanced nuclear ventures, is an atomic energy expert with small nuclear plant operating and design experience. He has engaged in technical, strategic, political, historic and financial analysis of the nuclear industry, its technology, regulation, and policies for several decades through Atomic Insights, both as its primary blogger and as host of The Atomic Show Podcast. Please click here to subscribe to the Atomic Show RSS feed. To join Rod's pronuclear network and receive his occasional newsletter, click here.

Similar Posts

  • The Atomic Show #124 – Barton, Wheeler, Sorensen – Clean Atomic Energy

    ByRod Adams

    On Sunday January 25, 2009, I invited three of the most active pro-nuclear bloggers for a chat about the state of the nuclear industry, clean atomic energy versus “clean” coal, renewable portfolio standards, effects of the current economic crisis. Charles Barton blogs at Nuclear Green and Energy from Thorium John Wheeler produces This Week In…

  • What do you do with the waste? – Kirk Sorensen’s answers

    ByRod Adams

    Gordon McDowell, the film maker who produced Thorium Remix, has released some additional mixes of material gathered for that production effort. One in particular is aimed at those people whose main concern about using nuclear energy is the often repeated question “What do you do with the waste.” Many people who ask that question think…

  • The Atomic Show #141 – Thorium and other atomic topics

    ByRod Adams

    Robert Hargraves, Charles Barton and Rod Adams talk about the Thorium Energy Alliance Conference and other miscellaneous atomic topics. The conversation ranged from thorium, to uranium supplies, to chemistry versus engineering, to the history of Oak Ridge, to the unreality of energy solutions that require continuous cash transfers from the public to the developer. For…