text:
FAQ #3: What's Your Assessment of the Directed Energy Weapon (DEW) Hypothesis? |
Written by Jonathan Cole, P.E., Richard Gage, AIA, and Gregg Roberts | ||||||||||
Sunday, 18 May 2014 05:00 | ||||||||||
Some have suggested that much of the structural steel of the World Trade Center skyscrapers was turned to dust, or "dustified" – a term used by Judy Wood, the primary proponent of this hypothesis – with some type of directed energy weapon (DEW). Some of the observations cited by Wood include the voluminous dust created during the Twin Towers' destruction, the "craters" in WTC 5 and 6, "toasted" cars, and small holes in glass windows. While Wood and AE911truth agree that the official story of an "inevitable" collapse by gravity alone is impossible because it conflicts with laws of physics, we completely differ on the mechanism of the destruction. Crucially, once there is proof and consensus that the official story violates elementary laws of physics, our major scientific task has been accomplished. The remaining task is the political challenge of mobilizing support for a legitimate investigation. Of course, the science of the collapse of the Twin Towers and Building 7 can be advanced beyond the mere conclusion that the official story must be false, but it is imperative that anyone seriously advancing understanding of the mechanisms of collapse hew closely to scientific methodology. This is crucial to earn the 9/11 Truth Movement the public respect it deserves, rather than to cast it into the role of perpetrating "junk science." The scientific method requires us to look at all the available evidence and then assess various explanations for their ability to account for the evidence. At some point, just as in pure science, the inferior explanations must be discarded if there is to be continued progress in an investigation. It is our opinion that the DEW hypothesis is not just weak; it is not supported by the evidence at all. We provide only a general discussion here, referring the reader to references for a thorough understanding. A Hypothesis in Search of Facts One of the observations that seems to have motivated Wood to come up with her directed energy weapon hypothesis is that the debris pile at Ground Zero does not seem to be tall enough to contain enough steel to equal what was in the Twin Towers before they came down. She departs from verifiable fact quite early with this claim. FEMA, the Federal Emergency Management Agency, performed the first technical review of what brought down the Twin Towers and WTC 7. Even in its report, FEMA acknowledges (inconveniently for the official story, which cannot account for this fine destruction of the Twin Towers) that roughly 90% of the Twin Towers' mass fell outside their footprints. Indeed, the entire plaza was covered with steel pieces and assemblies. Some of the structural steel was thrown as far away as the Winter Gardens – 600 feet. Given all this, there is no reason to expect a taller debris pile at Ground Zero than the photographs show. Wood's belief that some of the steel must have been turned into dust rests on a completely spurious interpretation of the visual evidence. Her hypothesis is an attempt to solve a nonexistent problem. As we will show, it can be sustained only by additional poor analysis and leaps of faith, just as in the official explanation. Damage to Core Box Columns Many of the core box columns found in the WTC rubble had concave sides. Most were broken straight across at the weld points. Often, one side of the column's welds was deeply oxidized and even torn away. Explosions ripping across the weld points, as explained by Gordon Ross, present an explosive hypothesis that offers a mechanism with results resembling observations in the WTC rubble. • Be capable of a sufficiently sharp focus for it to attack all or most of the columns at a given level at the same time, but only the ends of those columns; • Be capable of having its target level move down the building without changing the angle at which it cuts the columns; • Be capable of having its target level move down at two-thirds of free-fall acceleration (as measured by David Chandler), and perhaps other acceleration rates; • Be capable of having multiple target levels, so that it could destroy the falling upper section of each tower while also destroying the lower section, to create the illusion that the upper section is crushing the lower section, even though that upper section is in itself being destroyed; and • Be capable of destroying only those connections between steel columns that still form part of the buildings' structures, leaving untouched the hundreds or thousands of steel assemblies and steel pieces that can be seen flying out of each tower both within and outside of the huge clouds. In addition to all these features, Wood's alleged secret DEW technology would have had to be able to pulverize most of the 180,000 tons of concrete in both Towers, and Building 7, and in the case of the Twin Towers, eject 90% of the buildings' mass outside their footprints. Such technology would also have to be able to account for the evidence relating to molten iron, nano-engineered energetic material, and the sights and sounds of explosions as described below. Why posit sophisticated secret technology to explain these observations, when some combination of thermitic incendiaries and explosives placed throughout the buildings can explain them much more simply, and without making wild assumptions? This is a clear violation of Occam's Razor, which says that the simplest explanation that accounts for all the facts should be given the greatest credibility. In fact, the destruction of the Twin Towers matches fully the characteristics of "high-order damage" as they are listed in the NFPA 921 Guide for Fire and Explosion Investigations: All three WTC skyscrapers were completely destroyed; the structural units (perimeter walls, etc.) were shattered; heavy pieces from the Twin Towers were thrown horizontally at 70 mph over large distances; and most of the concrete floors were finely pulverized. That the common concept of high-order damage is met by the evidence at the WTC means that explosions with a high rate of pressure rise occurred. The use of high explosives can explain all the evidence that matches the characteristics of high-order damage. The case for explosives is also supported by over one hundred orally recorded accounts by FDNY first responders, many of whom reported sounds of explosions and patterned flashes of light, and by many interpreting the skyscraper destruction as being caused by "secondary devices." Wood asserts that the steel "turned to dust." One of the key observations that she uses to support this conclusion is the dust that appeared when a portion of the North Tower's core finally came down about 12 seconds into the destruction of the North Tower, several seconds after the floors that used to surround that core structure had been pulverized or had fallen to the ground. Upon studying the video of the "spire," however, we find that the steel did not "turn to dust" (see, for example, the next-to-last segment in http://www.youtube.com/watch?v=7W0-W582fNQ). The spire clearly simply fell after being "shaken" – most likely by explosive charges, leaving behind, in mid-air, the pulverized concrete that had been resting on, or statically stuck to, the steel. As is well known, air resistance causes dust to fall slower than structural steel (note the final remaining column falling faster than the dust in the third photograph of the sequence). Also, if the structural steel was "dustified," one would expect to see at least some evidence for partially "dustified" steel members in the debris, yet nothing of the sort is shown in Wood's book or website. One would also expect a much higher fraction of the dust to be consistent with iron-rich material than the 5.87% maximum of iron-rich spheres detected by RJ Lee Group (RJ Lee; see below). The massive structural steel frames of the Twin Towers (100,000 tons each) were roughly equal to the mass of concrete in the towers. Since the proportion of concrete powder in the dust was found to be up to 30%, one would therefore expect a similar percentage of "dustified" steel, but none has been found. The "toasted" tops of vehicles Wood suggests that the tops and other portions of damaged vehicles near Ground Zero may also be attributed to DEW, yet doesn't provide a possible scenario as to how DEW might account for this phenomenon, particularly in view of the fact that the towers reached high above ground while the cars were on the ground. Partially unignited thermite, thermate, and/or nano-thermite falling through the air as it continued to react would have produced molten iron droplets. A still-reacting thermitic mixture drifting down onto the cars in the dust plumes could easily account for the singeing of their paint and even igniting the cars (since the highly exothermic thermite reaction can quickly reach temperatures exceeding 4000 °F). A reporter and a firefighter (see the last two links at the end of this article), and perhaps others, described the dust cloud as feeling hot – whereas Wood claims that the dust clouds were cool. Once-molten iron microspheres found in the dust Substantial quantities of once-molten iron spheres, up to 150 times the background level of iron in dust from other buildings in the area, were found and documented by the US Geological Survey (USGS) and The RJ Lee Group. RJ Lee found the microspheres in amounts up to 6% inside the skyscraper across the street from WTC 2. Other scientists estimate a total of 10 tons to 100 tons of microspheres altogether throughout Lower Manhattan. These spheres were so plentiful that RJ Lee used them as a "signature component" of the WTC Dust, and the EPA discussed their use as signature markers. RJ Lee notes that the microspheres were "created during the event," that is, they were not created by welding operations during the cleanup of Ground Zero. The once-molten state of these microspheres indicates that they were created by temperatures hot enough to melt iron. Office fires and jet fuel fires, which do not produce such high temperatures, could not possibly have produced them. The chemical signature of the examined spheres matched the chemical signature of spheroids produced by common thermite and by red/gray nano-thermite composite chips found in the WTC dust, indicating that thermitic reactions took place as part of the towers' demise. The DEW hypothesis does not address this and cannot account for it because it is inconsistent with the extreme heat required to produce it. Molten metal is observed pouring from WTC 2 several minutes before its final destruction. Its bright white/yellow color (in daylight conditions) demonstrates that it is not aluminum, but steel or iron, and that its temperature far exceeds that which can be produced by jet fuel or office fires. FEMA's Building Performance Assessment Team report, May 2002, Appendix "C" documents molten iron invading the grain boundaries of the WTC structural steel. A revealing New York Times article called this "the deepest mystery" of the investigation. Thermitic materials (thermite, thermate, or nano-thermite) produce molten iron as their byproduct at temperatures of around 4,500 °F. They can easily cut through steel, and they can account for the ubiquitous iron spheroids. (See YouTube.com's "9/11 Experiments: The Great Thermate Debate".) The DEW hypothesis does not explain this phenomenon. In fact, Wood denies that such temperatures were ever reached. Active, unignited nano-thermite found in the dust An international research team found nano-engineered thermite, or "nano-thermite," in each of the four samples of dust examined as part of a peer-reviewed study. Nano-thermite, also known as super-thermite, was developed in US national laboratories in the late 1990s as an "energetic composite material," meaning it could serve as a pyrotechnic substance to ignite other energetic materials, as a rocket fuel, or as an explosive unto itself with advantages over conventional high explosives. One key advantage of such substances for the purposes of a surreptitious controlled demolition would be that it cannot be detected by conventional chemical tests or by trained, bomb-sniffing dogs. Another advantage is that these substances can be chemically tuned to adjust their shockwave characteristics, which presumably includes the amount and nature of the sound generated when they go off. The red/gray nano-thermite chips constitute direct evidence that supports the explosive/incendiary hypothesis. The DEW hypothesis does not explain why this engineered energetic material was found throughout the dust. DEW proponents merely wave away the evidence, which was carefully documented in a 25-page peer-reviewed paper, without addressing any of the specific points made in the paper. Independent researchers photographed particles of aluminum and iron oxide 1,000 times smaller in diameter than a human hair that were intimately intermixed and set in a bed of organic material capable of generating gas pressure when heated. They then analyzed these particles with x-rays and heated them in a calorimeter to the point where they reacted to produce iron-rich microspheres precisely resembling those found in the World Trade Center dust. These findings conclusively account for the observed high-temperature phenomena described in the next section.
Extremely high temperatures at Ground Zero are documented by various sources, for example in thermal images by MTI and NASA, USGS aerial photo 9-16-01 photographs, and by numerous witness accounts. The American Society of Safety Engineers reported that "the debris pile at Ground Zero was always tremendously hot. Thermal measurements taken by helicopter each day showed underground temperatures ranging from 400 ºF to more than 2,800 ºF." Wood denies that these temperatures were reached without addressing the ample evidence for them.
Wood attaches great importance to the holes that are visible in pictures of WTC 5 and 6, purporting to find no other explanation than exotic weaponry. These holes are easily explained by the thousands of tons of falling steel, smashing through the tops of the adjacent structures. Numerous steel perimeter column sections from the towers can be clearly seen inside these holes. Hundreds of eyewitness accounts of multiple explosions The many qualified witnesses to the sights and sounds of explosions are easily explained with the controlled demolition by explosive hypothesis – but not with the DEW hypothesis. Wood questions the credibility of the witnesses of explosions (amounting to hundreds) throughout the Twin Towers. Conclusion We do not support the DEW hypothesis because it is not supported by the available evidence. In contrast, the explosives/incendiaries hypothesis for the WTC destruction is well supported by the evidence. In addition, we believe the DEW theory raises far more questions than it answers, such as the energy requirements and other issues outlined in the suggested references listed below. Based on what we know today, it is our opinion that the destruction scenario that best addresses the evidence is some type of explosive demolition using some combination of thermitic incendiaries and explosives that were placed inside the structures. We also recommend this seven-minute video of Richard Gage answering questions about DEW: http://www.youtube.com/watch?v=y0D52_9WJbk Finally, we recommend the following technical papers for a more complete review of the DEW hypothesis. The Overwhelming Implausibility of Using Directed Energy Beams to Demolish the World Trade Center Dr. Gregory S. Jenkins Solving the Great Steel Caper: DEW-Demolition Contrary Evidence Dr. Gregory S. Jenkins Supplemental: DEW-Demolition Contrary Evidence Dr. Gregory S. Jenkins Reply to Reynolds & Wood by Steven E. Jones, 8/25/2006 A Response to Reynolds and Wood by Frank Legge 5 and 6 World Trade Center: What Caused the Large Holes Visible from Above by Jim Hoffman ERROR: 'Building 6 Was Cratered by a Huge Explosion' by Jim Hoffman Each Tower Disappeared into a Volcano-like Cloud of Dust by Jim Hoffman Dust Clouds: Descriptions of Dust Clouds in the Oral Histories by Jim Hoffman


text:
Brad Feld
- Depression and Entrepreneurs
- Looking For A Design HackStar for Startup Revolution
- Changing How We Think About Education
Amy and I wrote a meaningful amount about entrepreneurs and depression in Startup Life. Since we finished the final draft a few weeks ago, I've given several talks where depression came up as I've woven my own experience with depression into the short (less than 15 minute) version of my story. I've received a surprising (to me) number of emails from people thanking me talking about it publicly, along with my discussion of the anxiety disorder (obsessive compulsive disorder) that I've struggled with my entire adult life and that was severe during the serious depressive episode I had in my early to mid 20s.
So the idea of depression has been on my mind. It doesn't surprise me that I feel down and flat as I sit here in the Charlotte, North Carolina airport on my way to Lexington, Kentucky on day 16 of a 19 day trip. I'm tired, strung out, missing home, missing Amy, and running out of extrovert energy. I've had a great time with all the people I've been with and the events I've had around Startup Communities. I've had several extraordinary experiences like dinner last night in Toronto with a dozen fantastic entrepreneurs who I hope to have continuous involvement – as a friend and potential investor – in the future. But as I sit here, I'm surrounded by a lot of grey, and it's not just the clouds outside that are the remnants of the storm.
I've reached out to most of my friends in New York to check in on them. They are all doing fine even though a few were hit hard and are now effectively homeless as lower Manhattan gets cleaned up. I picked a spot in the airport far away from the TV – I couldn't stand the endless news cycle that mixed Sandy with Romney with Obama. I had some extra carbs hoping that would help – it just made me feel sleepy. Yup – I know what this feeling is.
I know many entrepreneurs who deal with different levels of depression. My close friend Jerry Colonna is extraordinarly eloquent about this and how it impacts entrepreneurs. Ben Huh, the CEO of Cheezburger, wrote a powerful post about his struggle with depression titled When Death Feels Like A Good Option. And I've had many conversations with other entrepreneurs about my, and their, struggle with depression.
For some reason we've embraced failure as an entrepreneurial trait that is ok, but we still struggle with acknowledging and talking about depression. Entrepreneurs function with a wide range of stresses and emotions that often have overwhelming intensity. In many cases, we are afraid of admitting depression, and are often highly functional when we are depressed. But that doesn't deny the fact that entrepreneurs get depressed. To deny this, is to deny reality, and that's against my value system.
I just went back and read what we wrote in Startup Life about depression and it made me smile. I'm really proud of the work that Amy and I did on that book – I think it is the best book I've been involved in writing (Venture Deals, which I wrote with Jason Mendelson, is a close second) and I'm hopeful that it has a lot of impact and value for entrepreneurs and their partners.
Just writing all of this makes me feel better. Thanks for listening. Time to get on the plane and go to Lexington.
Read more posts on Feld Thoughts »

subset: commoncrawl


text:
This tutorial is based off of the MSDN Article #ID: Q194873. But, for a beginner, following these MSDN articles can be intimidating to say the least. One of the most often asked questions I see as a Visual C++ and Visual Basic programmer is how to call a VB DLL from VC++. Well, I am hoping to show you exactly that today. I am not going to go over the basic details of COM as this would take too long, so I am assuming you have an understanding of VB, VC++ and a little COM knowledge. It's not too hard to learn; just takes a little time. So let's get started. The first thing you need to do is fire up Visual Basic 6 (VB 5 should work as well). With VB running, create a new "ActiveX DLL" project. Rename the project to "vbTestCOM" and the class to "clsTestClass". You can do this by clicking in the VB Project Explorer Window on the Project1 item (Step 1), then clicking in the Properties window and selecting the name property (Step 2). Do the same for the Class. Click on the class (Step 3), then the name property and enter the name mentioned above (Step 4). Your project so far should look like the folowing right hand side picture: Ok, now we are ready to add some code to the VB Class. Click on the "Tools" menu, then select the "Add Procedure" menu item. The Add Procedure window will open up. In this window we need to add some information. First (Step 1) make sure the type is set to Function. Second (Step 2) enter a Function name called "CountStringLength". Finally hit the Ok button and VB will generate the new function in the class. You should have an empty function with which to work. The first thing we will do is specify a return type and an input parameter. Edit your code to look like this:
Public Function CountStringLength(ByVal strValue As String) As Long End Function
What are we doing here? We are taking one parameter, as a String type in this case, then returning the length through the return type, which is a Long. We specify the input parameter as ByVal, meaning VB will make a copy of this variable and use the copy in the function, rather than the default ByRef, which passes the variable by reference. This way we can be sure that we do not modify the string by accident that was passed to us by the calling program. Let's add the code now.
Public Function CountStringLength(ByVal strValue As String) As Long If strValue = vbNullString Then CountStringLength = 0 Else CountStringLength = Len(strValue) End If End Function
In the first line of code we are checking to see if the calling program passed us an empty, or NULL, string. If so we return 0 as the length. If the user did pass something other than an empty string, then we count it's length and return the length back to the calling program. Now would be a good time to save your project. Accept the default names and put it in a safe directory. We need to compile this project now. Go to the File menu and select the "Make vbCOMTest.dll..." menu item. The compiler will produce a file called surprisingly enough: vbCOMTest.dll. The compiler will also do us the favor of entering this new DLL into the system registry. We have finished the VB side of this project, so let's start the VC++ side of it. Fire up a copy of VC++, then select from the menu, "New Project". The New Project window should appear. Select a "Win32 Console Application" (Step 1), then give it a name of "TestVBCOM" (Step 2). Finally, enter a directory you want to build this project in (Step 3 - your directory will vary from what I have entered). Click on the "OK" button and the "Win32 Console Application - Step 1 of 1" window will appear. Leave everything on this page as the default, and click the "Finish" button. One final window will appear after this titled "New Project Information". Simply click the "Ok" button here. You should now have an empty Win32 Console project. Press the "Ctrl" and hit the "N" key. Another window titled "New" will appear. Select the "C++ Source File" (Step 1), then enter the new name for this file called, "TestVBCOM.cpp" (Step 2 - make sure the Add to Project checkbox is checked and the correct project name is in the drop down combo box), then click the "Ok" button to finish. Now we are going to get fancy! You need to go to your Start Menu in Windows and navigate to the "Visual Studio 6" menu and go into the "Microsoft Visual Studio 6.0 Tools" sub-menu. In here you will see an icon with the name "OLE View". Click on it. The OLE View tool will open up. You will see a window similar to this one: Collapse all the trees, if they are not already. This will make it easier to navigate to where we want to go. Highlight the "Type Libraries" (Step 1) and expand it. You should see a fairly massive listing. We need to locate our VB DLL. Now, remember what we named the project? Right, we need to look for vbTestCOM. Scroll down until you find this. Once you have found it, double click on it. A new window should appear - the "ITypeLib Viewer" window. We are only interested in the IDL (Interface Definition Language) code on the right side of the window. Select the entire IDL text and hit the "Ctrl" and "C" buttons to copy it to the clipboard. You can close this window and the OLE View window now as we are done with the tool. We need to add the contents of the IDL file into our VC++ project folder. Go to the folder you told VC++ to create your project in and create a new text file there (If you are in Windows Explorer, you can right click in the directory and select "New" then scroll over following the arrow and select "Text Document"). Rename the text document to "vbCOMTEST.idl". Then double click on the new IDL file (VC++ should open it if you named it correctly with an IDL extension). Now paste the code in the file by pressing the "Ctrl" and "V" keys. The IDL text should be pasted into the file. So far, so good. Now, this IDL file is not going to do us much good until we compile it. That way, VC++ can use the files it generates to talk to the VB DLL. Let's do that now. Open a DOS window and navigate to the directory you created your VC++ project in. Once in that directory, at the prompt you need to type the following to invoke the MIDL compiler:
E:\VCSource\TestVBCOM\TestVBCOM\midl vbTestCOM.idl /h vbTestCOM.h
Hit the "Enter" key and let MIDL do its magic. You should see results similar to the following: Close the DOS window and head back into VC++. We need to add the newly generated vbTestCOM.h and vbTestCOM_i.c files to the project. You can do this by going to the "Project" menu, then selecting the "Add to Project" item, and scrolling over to the "Files" menu item and clicking on it. A window titled, "Insert Files into Project" will open. Select the two files highlighted in the next picture, then select the "Ok" button. These two files were generated by MIDL for us, and VC++ needs them in order to talk to the VB DLL (actually VC++ does not need the "vbCOMTest_i.c" file in the project, but it is handy have in the project to review). We are going to add the following code to the "TestVBCOM.cpp" file now, so navigate to that file in VC++ using the "Workspace" window. Open the file by double clicking it and VC++ will display the empty file for editing. Now add the following code to the "TestVBCOM.cpp" file:
#include <iostream.h> #include <comdef.h> #include "vbTestCOM.h" void main() { // Declare an HRESULT and a pointer to the clsVBTestClass interface HRESULT hr; _clsVBTestClass *IVBTestClass = NULL; // Now we will intilize COM hr = CoInitialize(0); // Use the SUCCEEDED macro and see if we can get a pointer // to the interface if(SUCCEEDED(hr)) { hr = CoCreateInstance( CLSID_clsVBTestClass, NULL, CLSCTX_INPROC_SERVER, IID__clsVBTestClass, (void**) &IVBTestClass); // If we succeeded then call the CountStringLength method, // if it failed then display an appropriate message to the user. if(SUCCEEDED(hr)) { long ReturnValue; _bstr_t bstrValue("Hello World"); // We can test this HR as well if we wanted to hr = IVBTestClass->CountStringLength(bstrValue, &ReturnValue); cout << "The string is: " << ReturnValue << " characters in length." << endl; // We can test this HR as well if we wanted to hr = IVBTestClass->Release(); } else { // Something went wrong cout << "CoCreateInstance Failed." << endl; } } // Uninitialize COM CoUninitialize(); }
If all the code is entered in correctly, then press the "F7" key to compile this project. Once the project has compiled cleanly, then press the "Ctrl" and the "F5" keys to run it. In the C++ code, we include the MIDL created "vbTestCOM.h" file, the "Comdef.h" file for the _bstr_t class support and the "iostream.h" file for the "cout" support. The rest of the comments should speak for themselves as to what's occurring. This simple tutorial shows how well a person can integrate VB and VC++ apps together using COM. Not too tough actually.
This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.
A list of licenses authors might use can be found here
library XAPI { // Forward declare all types defined in this typelib interface IXField; [ uuid(A6B99FCD-4D31-411A-A735-E7DC17AC1123), helpstring("XField Object") ] coclass XField { [default] interface IXField; }; [ odl, uuid(19DE3CA1-CD87-4A89-B323-CE37EA23E1FB), helpstring("Dispatch interface for IXField Object"), dual, oleautomation ] interface IXField : IDispatch { [id(0x000000c9), propget] HRESULT Tag([out, retval] long* Value); } }
typedef interface IXField IXField; typedef class XField XField; EXTERN_C const IID IID_IXField; MIDL_INTERFACE("19DE3CA1-CD87-4A89-B323-CE37EA23E1FB") IXField : public IDispatch { public: virtual /* [propget][id] */ HRESULT STDMETHODCALLTYPE get_Tag( /* [retval][out] */ long __RPC_FAR *Value) = 0; }; EXTERN_C const CLSID CLSID_IXField; class DECLSPEC_UUID("CB29D47C-A1FE-4803-A30C-68CA10058EC6") XField;
HRESULT hr; IXField * mXField = NULL; hr = CoInitialize(0); hr = CoCreateInstance(CLSID_IXField,NULL,CLSCTX_INPROC_SERVER,IID_IXFixField,(void**) &mXField); long value = 0; mXField->get_Tag(&value);
TestXAPI.cpp(101) : error C2027: use of undefined type 'IXField'

 _clsVBTestClass *IVBTestClass = NULL;

 HRESULT hr;
 CComPtr<_clsVBTestClass> IVBTestClass;

 HRESULT hr;
 CComQIPtr<_clsVBTestClass> IVBTestClass;

General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


text:
(Richard Melville Hall)
singer, songwriter
Born: 9/11/1965
Birthplace: New York City
Moby is widely praised for bringing techno music to mainstream American and British audiences. Raised in Darien, Connecticut, Richard Melville Hall was nicknamed Moby as a child because Herman Melville, author of Moby Dick, is reportedly his great-great granduncle. As a teen, he played in the hardcore punk band The Vatican Commandos and sang with the group Flipper. In 1991, Moby had a hit in the UK when he set the theme of David Lynch's TV series Twin Peaks to a house-derived rhythm and titled it "Go." Moby, his first full-length album appeared in 1992. In 1993 came the double-A side single, "I Feel It/Thousand," which won an entry in the Guinness Book of Records as the fastest single ever recorded, at 1,000 beats a minute. The albums Ambient and The Story So Far followed. Everything Is Wrong (1994) finally earned him the attention of the American press. Moby then abandoned techno to record a heavy guitar rock album, Animal Rights (1995). He made a partial return to techno with I Like to Score (1997). Play (1999), a fusion of hip-hop and pre-1945 folk music, reached No.1 in the UK. In 2001 he launched Area: One, a summer music festival that featured electronica bands.


text:
Tharu-Navy Cushion Cover
Our star patterned cushion has a distinctive graphic feel, with a laid back look with its washed and faded finish. The pattern is screen printed by hand on to chunky cotton canvas to make a refined, contemporary and stylish design that looks hand made and undoubtedly modern. Mix with other cushions in our range to create a stylish touch to living spaces, bedrooms or terrace. The cushion back is made from heavy cotton canvas in a neutral greige, and with an invisible zip. Comes without cushion pad. Our cushions are made by a small printing workshop in Colombo.
Dimensions -45cm x 45cm
Style No - UISPCCLA08000005
Fabric Composition
100% cotton
Wash & Care Instructions
Hand wash separately in cold water using a mild detergent. Squeeze lightly and dry flat.


text:
Lindan Mlambo, NatMIRC, University of Bremen, Alfred Wegener Institute Bremerhaven
GenusPodcast in english
GENUS (Geochemistry and Ecology of the Namibian Upwelling System) aims to clarify relationships between climate change, biogeochemical cycles, and ecosystem structure in the large marine ecosystem of the northern Benguela/Namibian Coast (sout-west Africa). The coastal upwelling system has high seasonal and interannual variability in atmospheric forcing, in properties of water masses on the shelf offshore the Republic of Namibia, and in oxygen supply and demand on the shelf. In consequence, concentrations and ratios of nutrients in upwelling water and their CO2-content have steep gradients in space and time. In the past, significant and economically severe changes in ecosystem structure have occurred which are in part attributed to changes in physical forcing, translated to the ecosystem by oxygen dynamics.
The GENUS project is funded by the German Federal Ministry of Education and Research (BMBF) and is an endorsed project of the Integrated Marine Biogeochemistry and Ecosystem Research (IMBER)


text:
Telligent Marketing Privacy Policy
This update to our Privacy Policy was posted on June 25, 2020, by Telligent Marketing LLC, a Missouri limited liability company, referred to herein as Teligent Marketing. While not necessarily applicable to us, our new Policy reflects our intent to comply with the new EU General Data Protection Regulation (GDPR) standards, with respect to information gathered through our website, telligentmarketing.com and any related subdomains we may use from time to time. By using our website, you're agreeing to be bound by this Policy. If you are not satisfied with or do not agree with our Privacy Policy, you should not use our Website.
"Non-Personal Information" (NPI) is information that is in no way personally identifiable and that is obtained automatically when you access our Website with a web browser.
"Personally Identifiable Information" (PII) is non-public information that is personally identifiable to you and obtained for us to provide you with a product or service. PII may include information such as your name, address, email address, phone number, location data, an online identifier, and/or one or more factors specific to your physical, physiological, genetic, mental, economic, cultural or social identity.
Our Commitment to Your Privacy
Our Privacy Policy tells you what PII we may collect from you, how we may process your PII, how you can limit our use of your PII, and your rights to obtain, modify and/or delete any PII we have collected from you. Except as set out below, we do not share, or sell, or disclose to a third party, any information collected through our Website.
Telligent Marketing is committed to the security and privacy of all our customers and website visitors. We take your privacy seriously, and we will work with you to ensure that you have a safe and enjoyable experience on our website.
Information We Collect
Information you Provide Us
We collect personal information when you request information about our services and products, interact with our Website forms/bots or customer service representatives, request delivery of white papers or other information, schedule an event or otherwise voluntarily provide such information through our Website or otherwise. This information includes the following categories:
- Your Personal Contact Information, such as name, phone number, email address and website address.
- Our services and products that you may be interested in purchasing, including possible scopes of work and fee ranges.
- Your Company Information, including company website domain/URL, whether you represent a marketing agency, whether your company is a current customer of certain of our business partners.
Generally, you will have control over the amount and type of information you provide to us when using our Website.
As a visitor to our Website, you can browse our Website to find out more about us. You are not required to sign in or provide us with any PII as a visitor.
Information Collected Automatically
When you use our Website, we automatically collect certain information by the interaction of your mobile device or web browser with our Website.
Like many other websites, we use "Cookies." A cookie is a small piece of data stored on your computer or mobile device by your web browser. We use cookies to identify the areas of our Website that you have visited. We also use cookies to enhance your online experience by eliminating the need to log in multiple times for specific content. Finally, we may use cookies to personalize the content that you see on our Website or to customize marketing and other information we provide to you.
Other Automatically-Gathered Information
We may automatically record information when you visit our Website, including the URL, IP address, browser type and language, and the date and time of your visit. We use this information to analyze trends among our users to help improve our Website or customize communications and information that you receive from us. If combined with other information we know about you from previous visits, the data possibly could be used to identify you personally, even if you are not signed in to our Website.
Google Analytics Privacy Policy
Our Website uses "Google Analytics" to collect information about the use of our Website. Google Analytics collects information such as how often users visit our site, what pages they visit when they do so, and what other sites they used before coming to our site. We use the information we get from Google Analytics to improve our Website, services, and products.
Google Analytics collects only the IP address assigned to you on the date you visit our site, rather than your name or other identifying information. We do not combine the information collected through the use of Google Analytics with personally identifiable information. Although Google Analytics plants a permanent cookie on your web browser to identify you as a unique user the next time you visit our site, the cookie cannot be used by anyone but Google.
Google's ability to use and share information collected by Google Analytics about your visits to our site is restricted by the Google Analytics Terms of Use. http://www.google.com/analytics/terms/us.html. You can prevent Google Analytics from recognizing you on return visits to this site by disabling cookies on your browser. https://tools.google.com/dlpage/gaoptout
Do Not Track Settings
Some web browsers have settings that enable you to request that our Website does not track your movement within our Website. Our Website does not obey such settings when transmitted to and detected by our Website. However, this does not change our compliance in any other way with our Privacy Policy.
How Information is Used
When we use or process personal data about you, we do so only as necessary to provide the services and products you use (e.g., to meet our contractual and legal obligations), or otherwise with your consent, to comply with applicable law, or to fulfill other legitimate interests of you or us as described in this Policy. Through our Website, you will be provided with the choice of which types of communications you will receive with us, and the ability to change those choices whenever you want. Some of the more common, specific uses of your information are described below.
Providing Requested Services and Products; Fulfilling Contractual Obligations
We may use PII to provide the services and products you've requested or to otherwise perform any contract we may have with you, including communicating with you about the scope of work, payment, or other related topics. When you create an account on our Website, buy a product or service from us, or otherwise agree to our terms and conditions, a contract is formed between you and us. To carry out that contract, we must process the information you give us. Some of this information may be PII, and we may use it to do any of the following:
- Verify your identity for security purposes
- Provide you with suggestions and advice on products and services
- Provide our products and services, which include updating, securing, and troubleshooting, as well as providing support. We also may provide your PII to third-party service partners, agents, or subcontractors that provide services that support our business relationship with you (i.e. payment processors, website hosting companies, third party content platforms, etc.), but those third parties will only receive information necessary to provide the respective services and are not permitted to use personal data they receive from us for any other purpose.
- Improve, personalize and develop our services and products
We process this information on the basis that there is a contract between us, or that you have requested we use the information before we enter into a legal contract.
We will continue to process this information until the contract or service between us ends or is terminated by either party under the terms of the contract or agreement.
Information we process with your consent
Through certain actions when otherwise there is no contractual relationship between us, such as when you browse our Website or ask us to provide you more information about our business, including job opportunities and our products and services, you provide your consent to us to process information that may be PII.
Wherever possible, we aim to obtain your explicit consent to process this information, for example, by asking you to agree to our use of cookies or to receive communications from us.
Sometimes you might give your consent implicitly, such as when you send us a message by e-mail to which you would reasonably expect us to reply.
When we communicate with you about our business, we will use the contact information you provided to us to discuss technical issues, new products and services, and other information of interest to you. We may also send you emails with useful industry information, promotional information about our business, or offers from us or our affiliates. You have a choice about whether or not you wish to receive communications from us. If you do not want to receive any or certain communications from us, then you can select your choices by ticking the relevant boxes situated on the form on which we collect your information.
Except where you have consented to our use of your information for a specific purpose, we do not use your information in any way that would identify you personally. We may aggregate it in a general way and use it to provide class information, for example, to monitor the performance of a particular page on our Website.
If you have given us explicit permission to do so, we may from time to time pass your name and contact information to selected third-party service providers who we believe may provide services or products you would find useful.
We continue to process your information on this basis until you withdraw your consent or it can be reasonably assumed that your consent no longer exists.
You may withdraw your consent at any time by instructing us using the contact information at the end of this Policy, using unsubscribe instructions provided in communications, or changing your elections within our Website. However, if you do so, you may not be able to use our Website or our services further.
Legally Required Releases of Information
We may be legally required to disclose your PII, if such disclosure is (a) required by subpoena, law, or other legal processes; (b) necessary to assist law enforcement officials or government enforcement agencies; (c) necessary to investigate violations of or otherwise enforce our Legal Terms; (d) necessary to protect us from legal action or claims from third parties including you; and/or (e) necessary to protect the legal rights, personal/real property, or personal safety of our company, customers, third-party partners, employees, and affiliates.
Other Legitimate Interest
We may process information or use it to communicate with you on the basis that doing so is necessary to achieve a legitimate interest, either to you or to us. Where we use your information on this basis, we do so after having given careful consideration to:
- Whether the same objective could be achieved through other means
- Whether processing (or not processing) might cause you harm
- Whether you would expect us to process your data, and whether you would consider it reasonable to do so
For example, we may process your data or communicate with you for any of the following purposes:
- Advertising and marketing to you, which includes sending promotional communications, targeting advertising, and presenting you relevant offers based on the information you provide or our prior dealings
- Operating our business, which includes analyzing our performance, meeting our legal obligations, developing our workforce, and doing research
- Record-keeping for the proper and necessary administration of our business
- Responding to customer complaints or service requests
- Responding to unsolicited communications from you to which we believe you would expect a response
- Protecting and asserting the legal rights of any party
- Insuring against or obtaining professional advice that is required to manage business risk
- Protecting your interests where we believe we have a duty to do so
We will continue to use this information for this purpose until the legitimate interest no longer exists or such use is not necessary to achieve the legitimate interest.
Our use of re-marketing
Re-marketing involves placing a cookie on your computer when you browse our Website to be able to serve you, an advertisement for our products or services when you visit some other website. We may use a third party to provide us with re-marketing services from time to time. If so, then if you have consented to our use of cookies, you may see advertisements for our products and services on other websites.
Disclosures to Successors
If our business is acquired or merges, in whole or in part, with another business, we retain the right to transfer your PII to the new business. The new business would retain the right to use your PII according to the terms of this Privacy Policy, as updated or as changed by the new business, subject to applicable law. You will have the opportunity to opt-out of any such transfer if we determine that the new business has privacy policies that differ materially from ours or that do not comply with applicable law.
Obtaining, Changing or Deleting Your Information
Access to your personal information
You may review certain information that we hold about you by signing in to your account on our Website. To obtain a copy of all information we maintain about you, you may send us a request using the contact information at the end of this Policy or, if available, through a tool on our Website. After receiving the request, we will tell you when we expect to provide you with the information, and whether we require any fee for providing it to you.
Remove or Change your Information
If you wish us to remove or change PII that you have provided us, you may contact us at the contact information at the end of this Policy or, if available, through a tool on our Website. This may limit the service we can provide to you.
Verification of your Information
When we receive any request to access, edit or delete PII, we will first take reasonable steps to verify your identity before granting you access or otherwise taking any action. This is important to safeguard your information.
Retention Period for Personal Data
Except as otherwise mentioned in this Policy, we keep your PII only for as long as required by us:
- To provide you with the services or products you have requested, or otherwise to perform or enforce a contract between us;
- To continue to provide the best possible user experience to visitors who return to our website to collect information and educational materials
- To comply with other law, including for any period demanded by tax authorities; or
- To support a claim or defense in any court or any legal, regulatory, or administrative proceeding.
Our Security Policy
Our Website is hosted in the USA and we conduct all of our business from any of our offices located in the USA and in some cases, outside of the USA. Accordingly, the information which you provide to us may be transferred to countries outside the USA or the European Union. By submitting your personal data, you're agreeing to the transfer, storing and processing of your data outside of the European Union or the USA. Your data may be transferred to countries that do not have the same data protection laws as the country from which you initially provided the information.
We have taken steps to build our Website using sophisticated encryption and authentication tools to protect the security of your PII. When we collect your PII through our Website, we will encrypt your PII before it travels over the Internet using industry standards as establishing for conducting secure online transactions. We also use industry-standard technologies such as secure routers and firewalls to make sure that your PII is safe. Unfortunately, we cannot fully guarantee secure data transmission over the Internet because of its nature.
Once we receive your PII, we have industry-standard security measures in place to protect against the loss or misuse of your PII, though again, we cannot fully guarantee against such loss or misuse. We strongly urge you to protect any password you may have for our Website and not share it with anyone. You should always log out of our Website when you are done using it, especially if you are sharing a computer with someone else or are using a computer in a public place.
Limitation of Liability
You assume the sole risk of transmitting your information as it relates to the use of this Website, and for any data corruptions, intentional interceptions, intrusions or unauthorized access to information, or of any delays, interruptions to or failures preventing the use this Website. In no event shall Telligent Marketing be liable for any direct, indirect, special, consequential or monetary damages, including fees, and penalties in connection with your use of materials posted on this Website or connectivity to or from this site to any other site.
Protecting Your Child's Privacy
We follow the Children's Online Privacy Protection Act (COPPA). Even though our Website is not designed for use by anyone under the age of 18, we realize that a child may attempt to access our Website. We do not knowingly collect PII from a child. If you are a parent or guardian and believe your child is using our Website, please contact us. We may ask for proof of identification before we remove any information to prevent malicious removal of account information. If we discover on our own that a child is accessing our Website, we will delete the information as soon as we discover it, we will not use the information for any purpose, and we will not disclose the information to third parties. You acknowledge that we do not verify the age of our users nor do we have any liability to do so. If you are a child, please seek the permission of a parent or guardian before accessing our Website.
Our Email Policy
We comply with the federal CAN-SPAM Act. You can always opt-out of receipt of further email correspondence from us or our affiliates. We will not sell, rent, or trade your email address to any unaffiliated third-party without your permission (except in the sale or transfer of our business).
Other Websites
Our Website may contain links to other websites. You understand that these websites are not under our control and are not subject to our Privacy Policy. These websites will likely have their own privacy policies, and we urge you to read those policies before using the website. We have no responsibility for these websites and provide links to these websites solely for your convenience. You acknowledge that your use and access of these other websites is solely at your own risk. It is your responsibility to check the privacy policies of these other websites to see how they treat your personal information.
Our services sometimes include preparing or recommending content for customers' websites that are built, hosted and/or maintained using a third party's content management system or other facilities, but Telligent Marketing does not host or control the content or operation of any customer websites. Telligent Marketing is not responsible for drafting, posting and/or enforcing our customers' privacy policies or determining whether the customers' policies or practices comply with applicable law. We are in no way responsible or liable for the collection and use of personal information by our customers from their websites or otherwise resulting from our marketing services.
Changes to Our Privacy Policy
We reserve the right to change this privacy policy at any time. If our company decides to change this Privacy Policy, we will post those changes on our Website so our users and customers are always aware of what information we collect, use, and disclose. In all cases, your continued use of our Website or our services and products after any change to this Privacy Policy will constitute your acceptance of such change.
Questions about Our Privacy Policy
If you have any questions about our Privacy Policy, please contact us as follows:
By email: info @ telligentmarketing.com
Our Mailing Address is:
Telligent Marketing LLC
12772 Corum Way Drive, Creve Coeur


text:
Lucknow to Kannauj Taxi Booking, One Way Cab from Lucknow to Kannauj, Lucknow to Kannauj at the best price. We specialist in one-way outstation taxi from Lucknow to Kannauj at cheapest taxi fare. Car Rental & Car hire from Lucknow to Kannauj is available for all car types, including sedans and SUVs.
We Offer Best Services
Customer provided ratings, Informed decision making, No surprises
24 x 7 Customer support, Instant booking confirmation, Transparent billing
Book in 3 easy steps
Search by car model, Book on web, app or phone
Top Cab Routes from Lucknow
Select Type to update price, included kms & extra fare
Top Cab Routes to Kannauj
Select Type to update price, included kms & extra fare
Related Links


text:
Break free of the bars that hold you caged !!!
Unless you risk and break free of the bars that hold you caged you won't gain something which can take you to even greater heights. Gather all the courage; dare yourself to challenge the limits and cross the threshold of fear as well as anxiety- something better awaits you at the other end. Those who wait for fruits to fall wait longer than those who pluck it off the tree. ~Latika Teotia