Ten Steps Back
This blog looks at the sign given to Hezekiah that showed he would be healed of his illness. This is the background story to soon coming headlines. Then details on this week's panic in the shop. Then progress on formatting new Bibles. Then a busy set of watch dates. Finally, a headline review.
Hezekiah's Illness
The link here is to 2 Kings 20 in the BRB. This is the chapter that deals with the illness of king Hezekiah. The replay of that king's reign begins on 2026-11-04, so Wednesday after this blog goes out. This will be the day after midterm elections in the USA. The story itself can be dated and will start to replay 2026-11-17.
The story begins with a prophetic word that the king is going to die. In verses 2 and 3 Hezekiah then prays and weeps over his situation.
Starting in verse 4 there is a long passage in green voice where we see that Hezekiah's prayer has been heard, 15 years have been added to his life and that Joshua is now going to start defending the city.
It is important to note that at the start of Hezekiah's reign, the city of Jerusalem, where this is taking place, had been the capital at least of the southern kingdom. But, by this point, the Assyrians had carried away as captive nearly everyone who lived in the region. Only those within the city had remained behind. Hezekiah was ruling a city-state, not a country.
That event is called the Assyrian Deportation. It times perfectly with the founding of the city of Rome. This is why the end of the Biblical chronology is Paul going to Rome. Paul is going to the lost tribes. This detail matters to understanding the 2002 replays of these stories.
In any case, returning to Hezekiah, he asks for a sign that he will be restored to health. That sign is how the sun will go back 10 steps. There are 5 such references to those 10 steps. The sun does move back, and Hezekiah is restored to health.
Sun Going Back?
This is one of 3 times where readers of the text might dispute the account simply because the event is hard to understand. The earth itself has what is called "angular momentum." Earth is spinning like a very, very heavy top. It has a great deal of momentum in that spin. So it is very hard to imagine the sun in the sky going back by any significant distance, say 10 "degrees" which might be the actual unit.
There are 2 other similar stories that involve events in the sky.
The sun stood still during the conquest of Canaan after the Exodus. See Joshua 10:12. This earlier story has the same problem. Angular momentum of earth prevents the earth from stopping. How could the sun stand still?
The final related story are rocks falling from the sky. See Joshua 10:11. This final example is easier to understand. The Perseid meteor shower still comes around twice a year and would be great rocks from the sky.
But what about the sun?
The most likely answer is that that there was a minor shift of the axis of rotation of the earth at these 2 events. Both accounts were written as viewed from earth. The first event is the standing still at the conquest. The second is the sun moving 10 degrees soon after the deportation during Hezekiah's reign.
I have covered pole shift physics in an earlier blog. The pole likely moves along a line between its current location and a location near the equator in central Africa. The earth's internal density is not smooth and the axis of rotation is bi-stable at or near these 2 locations.
The Giza Plateau is on the same line. Archaeological evidence points at the pole at both of these locations at various times in human history.
So assume these 2 events, recorded in the text, involving the sun, are minor, so settling, moves of the earth's pole. These were not full pole shifts, but similar physics. Both of these written accounts moved the axis of earth's rotation, but without major net change from what we know now.
Why Tell Us This?
Why would we need to know these things? Why is it written in the text?
In both of these accounts there is a major change in the location of Jacob's heirs going on at the same time.
The first, when the sun stands still, is after the Exodus. This when Jacob's heirs where moving from the Nile river water shed into Canaan.
The second, Hezekiah's 10 steps, is when Jacob's heirs were moving from Canaan to Europe. This migration is what started early in Hezekiah's reign. Some went by sea, some overland.
The AUC calendar, measuring years from the founding of the city of Rome, begins at the same year as the Assyrian deportation early in Hezekiah's reign.
Weather
What really matters for that second move is to think of possible weather changes in Northern Europe. The north pole, most likely, moved the pole along the normal pole shift axis, but away from Europe out to the current location in the middle of the Arctic ocean. This would have cooled eastern Siberia and Alaska, but it would have warmed northern Europe.
These movements of the sun are likely changing weather patterns. The first made Canaan more fertile than in Abraham's day. This may have fixed the famine problem that caused the need for going down to Egypt. Egypt does not need much rain. The Nile waters Egypt. Canaan needs rain.
So a pole shift when going into Canaan probably allowed Lebanon to grow Cedars. Remember, Solomon ordered up Cedars from Lebanon to build his temple. Those trees grow with rain forest amounts of rain. This is not seen in modern Lebanon because it is after Hezekiah's 10 steps.
At Hezekiah's day, the pole shift probably makes Europe more habitable than it was previously. It was preparing Europe for Jacob's heirs. It was providing climate that would make Europe a home for the lost tribes. It was providing more habitable, so productive, lands for the lost tribes.
Since at least the time of Napoleon, European leaders, so Zionist bankers, have been attempting to conquer Russia in order to control more land and thus control more natural assets. Those assets ultimately pay interest on national debts. Europeans have barely enough productive land as it is.
So since moving north in Roman times, Jacob's heirs, the lost tribes, are now trying to move east. Putin is their presumptive villain because he controls the wealth of Russia.
Europeans are also, curiously, attempting to control the rest of the world. This is the Zionist thread that starts with the Jebusites in the last 3 chapters of Judges.
All of these general trends are what show up in the prophetic replays of these same scriptural stories. They showed up dramatically in 2002 and they are likely to show up again between now and the end of 2026. More on those details below. Let me turn to other events around the shop this week.
Panic In the Shop
So after last week's blog went out I did an update to the operating system software for the main computer in shop. This is a big machine. Lots of CPUs and memory. It is used for 3d design and will be used for audit. It can be used for media once we have something to show.
For the first time in maybe 30 years of doing nearly weekly updates to Linux machines, the software update on that machine failed mid way with an error message. This was an "Oh sh*t" moment that is never supposed to happen.
It immediately suggested to me that someone was being careless in Denver where PopOS is built. I did a search on the problem and found that yes, indeed, there was a customer facing update failure going on with this week's round of updates to PopOS.
There was also a suggestion about how to stop key parts of the update from becoming active. After that triage, that machine would still risk reboot issues. It would then sit, remaining in wait for the next update.
Because this looked strongly like a careless human error on their part the problem might not go away next time. This was a very serious problem. It messes our work flow.
Done
Ryan and I have been to the offices in Denver and met some of the people involved. We've waited through years of delay getting this system rewritten. Now, they are not doing simple testing before release? I don't know for sure what is going on, but I can make some guesses.
When they decided to write a new desktop for Linux some lead programmer and someone with money agreed to the scope of work. The tech guy committed to building it, and the guy with money estimated his budget, along with some risk based on the man-years of work that would be involved.
What we know now, is the project became years late. So we know the budget was blown. We know the tech guys involved did not estimate the real work. They must have been surprised. They did not fully understand their task.
Crazy, but Ryan and I have been through similar things. In our case we are on a discovery process. We are walking by faith. We have no real clear idea what the scope of work might ultimately become. We take each day 1 at a time. Our own work probably impacts our patience with these long delayed updates to PopOS. We have given up estimating when we might be finished. We press on.
Software operating systems are different. They work fine if you just leave them alone, or at least only fix bugs. Doing an update to software is not normally a religious task. The scope of work should be bounded.
Once any big software project becomes years late, the budget gets blown, trust in the technical plan fails and then people involved start to leave. The failure we saw this week with PopOS looks like a rookie mistake. This happens because the original team who knew what they are doing are gone.
Both Ryan and I immediately reacted to this problem in the same way. We need to switch to a different version of Linux. We both immediately thought of switching to some "flavor" of Ubuntu. We left Ubuntu years ago because Ubuntu itself was having similar problems figuring out what they were doing with major system updates.
But, it has now been years. Ubuntu is the stable Linux. Time to go check again and find something that can replace PopOS.
Kubuntu/Ubuntu Studio
We were pleasantly surprised at the variety of Ubuntu flavors that could be downloaded from their website. Two of them caught our attention. Kubuntu will go onto our laptops here soon. (With no updates to PopOS until we are ready for that.)
The shop computer is different, and we have now installed Ubuntu Studio on that machine. This solved the immediate reboot risk. But it upgraded that machine in 2 important ways. Ubuntu Studio has the same basic desktop as Kubuntu, so it will match the laptops. But Ubuntu Studio also includes by default all the apps needed for any type of artistic and media content creation.
This includes a rich set of apps for image, video and sound. OBS, for live streaming video, for example, is installed by default. 3d work is part of that class of app, and OpenSCAD is also up and running fine on this new system.
This choice for a new OS gets us prepared for doing media work, which we haven't done since everyone was trapped at home during Covid.
Curiously, Ubuntu Studio also has a real-time kernel. This to support real time streaming related apps. This was attractive for the shop computer because it may help with our upcoming audit work.
I was also worried some about support for 4 monitors. This has been a major problem in the past. Turns out everything installed and ran absolutely fine.
The only real configuration was telling the system which monitor was in what visual relation to the others. A drag and drop operation in one of the display configuration apps was all that was needed for the monitors.
Speed
This new software seems to be getting better performance out of the graphics stack. This is especially noticeable when spinning around the Sower and Reaper models that I am currently testing on the 3d printers. There is no obvious reason why this would be so. There are several possible choices for graphics support, and the default choice, which is what we are using, seems to be better than PopOS.
This may have been a fortuitous update that matters with work still to come. Audit may get better performance out of this setup. We are also now ready to again deal with telling our story on video.
Backup Hardware
We were not sure if replacing the entire OS would risk user data on the computer itself. So I was ready with a new hard drive, expecting some drive to become a backup drive to our Git server where we manage our projects. This was one feature of that shop machine that was still needing to be added. So this was the time. Note that new hard drive prices were going up by the day this week on Amazon, presumably a supply chain issue.
Turns out the new system would install along side the current PopOS on the current system hard drive. The home directory was already on its own drive, so user data simply moved from one system to the other. So the new hard drive went in as the new backup drive.
Our whole setup in the shop is much better. Some of the utilities are a little different, which I am learning. The laptops will get updates here in the next week or so. So normal work is slowed down, but the panic is over.
That machine needs a UPS, which will get added soon.
New Bibles
So Ryan and I are working through a set of tasks to bring new Bible versions into the VR and BR apps. There is a coding part to this task, which I am taking care of. Ryan is curating the list of interesting Bibles and then he is handling specific needs of markup and styling to show off these Bibles in our apps.
This week we were able to run a new version (for us) of the KJV through our new set of tools. This is an important milestone since we are starting over with this family of Bible related files and the code and styling to handle them.
This KJV text has lexicon data with Strongs Numbers for the Hebrew Old Testament. The New Testament has Greek Strongs Numbers. The New Testament also has Robinson Morphology and Greek Words. So there is quite a variety of data coming through our new tool chain, not just the historical running text of the KJV.
Interesting Issues
It turns out that the formats used for most Bibles are a computer standard known as XML. Years ago, as a young programmer, my boss asked me to review the spec for what was then a proposed standard for XML.
I panned the document. The designers of XML could not decide if they were building a textual format for database related data, or else a markup standard for documents.
White space handling differs between these uses and this is where XML fails. The JSON file format eventually won out over XML for data base like storage in a text file. JSON has no concern for preserving white space.
HTML handles textual style markup better because it starts with the assumption of a string of letters that are being marked up in some way. HTML is modeled from XML, so they are similar.
Our Parsing Problem
In years past, we parsed some of these files already. XML parsing was not something in a library and we were mostly concerned about the running strings of text. So our old code treated the problem as a string substitution problem. This was messy, not configurable and tuned to each version of the Bible.
So, these days, XML parsing is done by a (huge) library. The installed size of the XML parsing library is twice the size of a typical Bible. This is cringe, but oh well.
So our new code for handling these files crawls through layers of header related stuff that provides data about the version. In these early layers, white space is in the way and must be skipped.
So code starts with figuring out structure, like testaments, books, chapters and verses. The code for this level of the problem is very different than inside verses.
Inside verses is where white space, so stuff between tags, very much matters because this is where between word punctuation from the KJV English is found.
The basic code for all of this is now done and running. We are still testing on the KJV, but so far everything is looking good. But, by faithfully parsing the inbound XML files, we run into a new class of problem.
Ordering Problems
There has always been a theoretical tag ordering problem with Bibles coming from XML. The structural elements eventually reach verse related content. These are marked with a verse number inside a verse related tag. This creates real markup that is seen in our Bible related apps. You know it as the verse number that you can see.
What follows the verse number is the content of the verse that human readers actually care about.
So imagine if the verse starts with a paragraph break.
If we are faithful to the inbound XML file, the verse number will come before the paragraph break. This will put the actual verse number on the tail of the previous paragraph. Why? Because verse number comes before the paragraph break.
This has always been a tricky problem because the needs of real humans reading real text is not actually met in the XML file format for the raw Bible. There must be a conversion step to clean up stuff like this.
Our fix this time around, with this new code, was to build in a "regular expression," so regex, based post processing step that can clean up anything mixed up in the raw output. Ryan now knows how to run regex edits so he can work this problem as a configuration issue instead of me writing it case-by-case in code.
Our overall work flow is dramatically better. We are still working out the full tool chain, but converting bibles is no longer a coding task, but a configuration task based on the needs of the inbound texts. This is a major change in our work flow. Bibles in our apps will be much better here soon.
Interlinear Data
Our existing tool chains support inter-lined data that follows along with each word in a text. Typically, this second (or possible more) row of words is a second human language. But, this same format can also be used for lexicon data, like Strongs Numbers.
Our existing tools for this sort of data were found wanting as I was starting to bring up the Paleo Bible. The problem for the Paleo Bible comes from how we previously treated this data as "tight" to the base line of text. No markup was allowed inside the couplets that mark interlinear data. If a word was colored red, then the inter-lined data was red as well.
The Paleo Bible needs letter level markup because that markup will show audit results. It will also show spell correction in the base Paleo string when spelling changes are needed to bring words into audit. It may also be used to show parts-of-speech, especially suffixes.
So I have had a Paleo Bible related to-do to rebuild our world to allow nested tags inside the couplets that make up inter-lined style data.
It turns out the KJV text we are using for our current work also includes markup inside the couplets that mark lexicon related data. So even the new KJV markup needs this problem fixed.
So, along with everything else this week, I was able to get the code changes for this issue at least sketched out. This is not easy to debug because it happens as part of a much longer tool chain. But, this problem is on the way to being fixed.
Match Dates
There were no obvious headline related watch dates this past week. But, the main headline was elections in Israel. This is a big deal because the public in Israel had some chance to get rid of Netanyahu.
At this point it looks like there was no clear winner in that election. Netanyahu will be running a care-taker government. There may yet be another election should the various parties involved be unable to find a coalition.
The Arab parties had an unusually high number of votes. Netanyahu blames this on criminal behavior. (Psychologists call this projection, I digress.) Any Jew in Israel who wanted to protest no clear choices in the main parties probably just voted for Arab parties.
There were rumors of the IDF leadership telling Netanyahu that they would not go to war with Iran until after the election. That threat seems to have held. It would naturally continue to hold until after a government is formed.
But, since the American government is Netanyahu's personal vassal, war with Iran is now expected to start via the Americans. Israel will join the war after Iran retaliates. This is currently widely expected the day after the US midterm elections. Even if off by a day or so, this will hit the next prophetic dates. Lets look at those.
Watch Dates
Our next watch date is 2026-11-03, this is the Tuesday after this blog goes out. This is the replay of the last year of Ahaz. This already has known fulfillment, which is the midterm elections in the USA.
Republicans are expected to be roundly moved out of office because of Trump's exceptionally poor performance as US President. History may judge him as the worst US president ever to hold office. The main issue is how Trump works for the Jews of Israel. The US public is now on to this crime in ways not possible previously because of social media.
Never mind that most of the US Congress also works for Israel. So there is no way to vote out of a foreign occupation. Many voters know this and do not intend to vote at all.
Philistine Prophecy
There is a dated prophetic story directed at the Philistines given in Isaiah 14:28. The date given is the year of the death of king Ahaz, so on the date of the US elections, 2026-11-03.
We don't currently list this as inspired, so it is unclear if we would expect any matched modern fulfillment. This does not appear to have matched headlines in 2002 when this replayed before.
Modern Philistines are likely just modern Israel, not Gazans as Zionists would hope. So if this does see headlines, it would involve Israel or else Israel's Zionist backers in much of the rest of the world.
If someone waits until after polls close in the USA to start another war in West Asia, this passage might suggest trouble starts at that date for Israel.
Key ideas from that passage.... "Out of the roots of the Hivite (so Jebusites, so Israel) comes a flying snake. (So rockets.)" It then mentions cries for the city. Gazan's don't have a city, but Israel does. (So Tel Aviv or Haifa.) It also mentions Zion, so Jebusite Jerusalem. This prophecy is all about the Hivite, so modern Zionists.
Historical Events
Also, in history, there was an Assyrian invasion of ancient Israel that lead to a 3 year siege of Jerusalem. The Assyrian deportation was going on across that time. It peaked at 10,276 AA, which will replay on 2026-11-09, so about 1 week after the US election.
Note that in September, 2002, when these same stories replayed, we find the Palestinian cabinet resigned on the death of Ahaz. We find Switzerland joining the UN, breaking their neutrality. We also find US President Bush going to the UN to give a speech about the USA going to war in Iraq. The US Congress would approve war in Iraq about a month later. The actual ground war with Iran would take another couple months to organize. American troops just left Iraq from that previous prophetic invasion here in the past few months.
Since we are now replaying the start of the 2002 US war with Iraq, we should watch for a similar war this time around. This time it looks to be against Iran. It does not look like this will be a quick war. It may not get full congressional approval until after the new congress is seated.
Notes On Iran
Certainly this idea of war with Iran is being talked up across much of the Zionist world. Like the previous Iraq war, a ground war with Iran could draw on for years.
Iraq became an occupied country and the military side of that occupation only ended here recently. Politically, Iraq is not part of current summit meetings suggesting Iraq is still politically controlled by Zionists.
The difference this time around is we are reaching the end of the prophetic intervals dealing with Babylonian occupation of Jerusalem that began in 1948. So Iran has a better chance of both following the same prophetic stories, but with a different eventual outcome.
Hezekiah's Reign
What starts late next week is one of the strangest dated stories on the timeline. This is what depopulated ancient Israel and started ancient Rome. It is highly likely we see some sort of cluster of related prophetic headlines.
2026-11-04, so the Wednesday after this blog goes out is the start of Hezekiah's reign. His reign will last through 2026-12-02, so about a month.
Within this reign is also the famous story when the sun goes back 10 steps, as I introduced at the top of this blog.
The date of the sun moving was in 10,284 AA, and replays on 2026-11-17.
2002 Headlines
Those prophetic stories replayed in 2002 with the European Union gaining 10 nations, 10 steps, in the east. This is essentially the match to the founding of Rome. This time, the match was an expansion of Rome headed east.
The EU was looking east, and the prophetic story would suggest the EU was looking backwards. The sun went back, so east, toward the sunrise, 10 steps.
European Zionists are currently looking to conquer Russia using Ukrainian proxies. They are still looking backwards. The EU is afraid of death, like Hezekiah.
Any headlines out of Europe for this prophetic set of stories would match the setup for the formation of Roman Europe. We may see headlines from there, watch Ukraine. The EU and NATO are generally attempting to include nations from the south of Russia. This is another venue to watch.
At nearly the correct dates in 2002, President Bush gave a speech at the UN in defense of his soon ground invasion of Iraq. Bush did not yet have congressional support, nor were the troops actually ready. That war actually began in March, 2003.
Iran is a more formidable foe than Iraq because of its underground bases. Shia Islam is also called out as winning in the Aramaic version of Revelation.
Trump has already given a UN speech on war against Iran, but he may speak more. He likes to babel.
Shop Work
The first fully working draft of the Sower model was finished this week. It is built using scrap plastic. I gave up trying to do this draft all in one color. Best to just keep using up scrap. It has no burrs, which is good. It has better choices for sectioning around the spine. Watch for pics on Telegram.
Curiously, I used up a spool of brown that had a flake finish. Not being white showed off issues with where one of the sectioning related cut points was located near the bottom of the spine. Because the parts print differently on the 3d printer bed, they have different finishing grain. This does not matter for white, but it does matter for more exotic plastics. To allow for exotic plastics, that cut point needed to be tucked up higher out of sight.
That cut point is fixed in the design files and will be printed when the sower is done in final silk silver plastic.
The Reaper is now on the 3d printers. It is thought to have all the same updates as the Sower, but the Reaper must still be tested. So this version is also being run with scrap plastic. Ryan's dad gave me some scrap plastic that should be used up this week. (One such ancient spool is so bad I may need to throw it away.) In any case, done with the sower, onto the reaper.
Ryan's Laptop
Ryan has started the process of updating system software on his laptop. He is changing out the drive so it is a fresh install. Once he has had some time to get familiar with this new Kubuntu setup, I will follow with an update to my own laptop.
Headline Review
The following caught my attention this week.
PHP Vulnerabilities
What Was Hacked?
The whole internet has been crazy with problems with broken websites. This is from a security vulnerability in PHP, the earliest and some think still the most common language for building websites.
I used PHP when I first started building bibletime.com. Microsoft's browsers were horrible pieces of garbage. (Windows is still a horrible piece of garbage.) Web servers had to compensate when someone visited from one of those garbage MS browsers. PHP was about the only choice for solving that problem.
Banks, in particular, also needed PHP for the MS browser problem. But, for them, PHP could then connect to their data center back end computers... You can see the theoretical mess created by PHP back doors when it comes to money related websites.
All you really need to know about PHP is that it was written by a company in Israel. At the time, I did not know why that mattered. Now I do. Now I always want to know where something is from.
We stopped using PHP after bibletime.com was hacked via an earlier bug in PHP. The tooling for figuring out the actual source, and thus patch, of the bibletime.com PHP mess was more trouble than just rebuilding the website without using PHP at all.
We also stopped using the production server for nearly anything other than serving static pages. The settings system we now have in our apps allows them to run off line. In the old days, that would have been server side in PHP. The only interactive code in our current server is code to pass on blog signups and feedback. This is done via a normal email server that we do not control. So we have very, very little security exposure on our server. Rebuilding it, should we ever be hacked, is also trivial.
The link above is Mike Adams speculating that the current back door in PHP may have been deliberately put there by command of the NSA. He may have the wrong 3 letter agency, maybe even the wrong country, but this is how the Patriot Act actually works. So the process of patching PHP is the process of finding a new back door that can be added as the old door is removed. This is why AI cannot be open sourced for very much longer and why only Zionist government agencies will ever control AI. Though fun, AI is unfit for purpose.
The second link above is to the start of a thread on X with a list of examples of websites that are impacted by this. Note most of these have been around for decades. "If it ain't broke, why fix it?" I would have trouble imagining any company starting from scratch using PHP these days.
French Protests Larger
More
Protests in France have grown well beyond students and looters. This link is to a Press TV post on Telegram with video of crowds in Paris. Maybe 1,000,000 in that crowd? Very large unscheduled gatherings are usually prophetic, even if we don't know why.
Massive Protests in Tel Aviv
Bigger A Day Later
Netanyahu seems able to draw protests against him too. Here is video from Tel Aviv. Second video a day later and much bigger. Israelis don't like Netanyahu.
Starlink Terms of Service
The debate over the use of Starlink for war is now carrying the correct vocabulary. This is now a "terms of service" issue. Nice. Most new tech has trouble with what the terms of service should be. Starlink is now getting the details worked out. Should apply world wide. SpaceX share holders really don't want Aborigines in Australia using Starlink to bomb Brisbane. If the US military wants to do something different, fine.
Pagosa Springs Floods
The link here is to a Youtube video with video of flooding in and around Pagosa Springs, Colorado. Ryan and I have done some Tabernacles in a campground just upstream from that town. A few readers here were there with us.
Most of that campground was about 2 feet above the river. These floods are over 15 feet. Likely, they buried the main campground building. Sad to see. This is considered a 100 year flood. Last seen at these depths around 1915. The world is forever changing.
Iran Plans Assassinations
This link is to a post on X. It suggests Iran has new plans to assassinate American officials. You can see from the feedback to this post that nobody believes such claims any more. The US government itself does these things and is NOT a trustworthy source of such news.
Doesn't Matter, I'm Jewish
This link is to a PressTV post on Telegram. This is a clip of a video of a woman pillaging stores during protests in France. A Muslim man confronts her and says this is wrong, using a technical religious term. Her answer is that since she is Jewish, she can take what she wants. Tell me again, which religion is righteous?
Lula Win in Brazil
Another press TV video on Telegram. This time of some crowds in Brazil celebrating the election victory there. This win is anti-Zionist and pro BRICS. First in South America since Trump. Jews have generally been taking over South America.
Egyptian Parliament Agrees to War
Egypt needs to go to war to match the 70th anniversary of the 1956 war against Israel. The issue had been passed to the Egyptian Parliament. This link reports they have agreed to war against Ansar Allah via support for Saudi Arabia. So Egypt is now Zionist. Wrong way you guys.
Zionists To Tehran
So the Zionist delegations from Turkey, Saudi Arabia and Pakistan have now visited Iran. There are times when the Iranians probably should say no to such meetings. In any case, here is the link. This may be an attempt by Zionists to take over Iran by covert means. Anything is possible.
Podcast commentary hopes this meeting was an attempt to figure out how to deal with Israel. We can hope.
Turkey Maritime Deal
Turkey and Libya have drawn lines in the sea to carve up the undersea wealth to themselves. This link has more details. This might be the predicted sea boundary headline that marks soon war with Turkey. This is not exactly the 6 mile prediction.
More Lines Leaving Ukraine
More photographic evidence of great crowds trying to leave Ukraine.
Bolsonaro To Miami
The looser in the Brazilian election fled to Miami. This post on Telegram has a pic of him getting off the private jet in Miami. Why would an honest candidate in Brazil need to flee to Miami after such a loss? Many are using his flight as evidence he is an American Zionist puppet.
More Later,
Phil