Where Did The Towers Go? - Lather

Words
310
Reading
2 min
Listen
Play
7M

Where Did The Towers Go? - Lather

Source: https://mysticbazaar.substack.com/p/where-did-the-towers-go-lather

In earlier articles I have looked at observable evidence pointed out in Dr Judy Wood’s book, Where Did The Towers Go? I shall link all the other articles at the end of this one. This time I am introducing something she describes as ‘Lather’. It is what looks like a fine frothy material seen escaping from intact buildings and is most clearly seen from WTC 1 before its destruction and from WTC7 throughout the day, behaving in ways that don’t resemble smoke from ordinary fires.Dr Woods describes what she calls the ‘lathering up’ of WTC 1 just after WTC 2 had been destroyed. From the image below you can see that this points to lather like smoke coming from one side of the building, even through solid walls and continues up until it’s destruction.Below is a clip of Dr Wood From her presentation at the Breakthrough Energy Conference in 2012, explaining Lather.Lather matters because it is observable. You don’t need to agree with Dr Judy Wood’s conclusions to see that what is coming out of WTC 1 and WTC 7 doesn’t behave like ordinary smoke from fires. It emerges from intact walls, avoids broken openings and persists for hours and appears to move with purpose rather than drift. At the very least it tells us the buildings are undergoing an internal process that hasn’t been properly explained. As with the other evidence I have covered, lather isn’t about speculation, it is about noticing when the official story stops matching what is right in front of us. You can see more observable evidence by looking at the article below, which lists a lot of the evidence you can see for yourself, with pictures and short videos.Leave a commentShare

Image 1

Image 2

Image 3

Image 4


🔐 Cryptographic Verification

Archived URL: https://mysticbazaar.substack.com/p/where-did-the-towers-go-lather

 CONTENT HASHES:
  SHA-256:  b3e22a27b348cd8f8501d23362d0717f48d4062e1b971a2d480d4b5896075e96
  BLAKE2b:  70cc4b6078b7b5abf3cee1f433943ca608d40c0c2a816eaf4f0fcc14372d9234
  MD5:      0f62abd0c5c6170bd123a4813a9401c5

 TITLE HASHES:
  SHA-256:  42f53f6255343480b5e6863ed56bdfbb1bc327aa94bcd04fecc42df83021b578
  BLAKE2b:  734cff7ea29fc6785d6ddf5ab8d4cbad8d15c6507a07adb78eb580300f8bb28e
  MD5:      d6c38d7b5df3ed365a09181e7093c13c

 INTEGRITY HASHES:
  SHA-256:  737e45ffc1a76e124fef6a595172e43a095587d24ac12babbc7c34dcfbf515aa
  BLAKE2b:  31eaad2b2b3719bb09e80d67257b88ce2ac08a6d04f5ab4f8f1951f0163d57f0
  MD5:      ff7a454e4286b65813b98d49a113e246

Archived with ArcHive - Client-side cryptographic archival system