App Parade

This blog introduces major upgrades to all of our apps. We start with the Story Grid before moving down the whole list. Then notes on the Paleo Bible, especially issues with names. Finally, a headline review.

Story Grid: 494

The big change with the Story Grid begins with changes that expose the current story to the URL for the app. If you are familiar with that app you know most of the stories are shown in "asides" which are also known as pop-ups. Previous to this week, those asides could not be reached from outside of the app. Someone using the app was required to tap the Story Grid square and then see the aside.

So now, as someone moves around in the app, the URL for the app changes to reflect the currently displayed aside. This is a powerful change, which allows all sorts of fun uses. It may be easiest to see with an example.

The link here is to the Story Grid app as normal, but now specifically to the Qu-Qu tile. This is number 494. Note that if you follow the link, not only does the app itself come up, but also that story is displayed. It is open and ready to read.

This is a very nice addition because it allows external references to any of the content inside that app. There are no longer any pages at all in that app. As far as the URL is concerned there is only ever just 1 page.

External Cites

If you poke around in that app and watch the URL you will see how the URL changes based on where you are in the app. The URL is now visibly maintaining the internal state of the app. This allows the URL to be copied around and kept anywhere. Following the URL back to the app will restore the state to match the URL. This makes any external cites easy to do. It has a few other interesting implications.

Browser Back

Not only does this give external access to what was an internal feature, it also puts the pattern of movement between asides into the browser's history. This enables the browser's "back" function to go backwards through that same aside history.

Supporting the browser back button suddenly became important once we redid the story related tiles. These are now much easier to use. But a common use case is to chase down related stories and then back up to the main story being studied. This is the most common use pattern for studying the story folds. Serious users, like Ryan, really want to have this feature in the Story Grid app.

No Back Button

There are some situations where there is no browser back button. The browser itself might not provide a back button. Apple's browser, at least traditionally, has not supplied a back button. Apps that are installed outside of the browser also have no back button.

So we have also added a "back" button inside most of the story related asides found in the Story Grid app. Poke around and you will see it. This makes the most typical study path evident and easy to reverse.

Tracking Current Tile

Moving around between stories in the app also causes a highlight to mark the current tile in the main grid. This highlight causes the main grid to scroll around and follow the current aside.

Once the current aside is closed, that highlight remains on what was the active tile.

This is another important feature because it allows anyone using the app to clear the current aside in order to study the general location on the main grid. But once out of a particular aside, that highlight indicates which story needs to be tapped again in order to return to the aside that was just active.

Again, this is all function needed by anyone serious about learning the grid.

Story Next and Previous

For all of the story related asides, there is also now a pair of arrows in the aside. These are in the top right, under the X that closes out the aside.

These arrows move in story number order. The left arrow goes down by 1 story. The right arrow goes up by 1 story. This has been added to make it easier to study story sequences.

The stories in each row of the table advance by 1 letter of the alphabet. So a common study for any given row is to read each story in sequential order. This allows the reader to spot the content advance that tracks the change in the letter. It is possible to read all the way through the Testimony using these arrows.

I read through the Qu row as a devotional to try it out. This is a nice new feature for this sort of scripture study. For that particular row, each story carries some aspect of the meaning of the letter Qu. It then also brings in content and meaning based on the second letter.

Right now, stories are still settling into their places. Eventually, once story placements are certain, this becomes a very serious study tool.

Replacing Study Bible

More and more, we are seeing the Story Grid app as the inspired replacement for what are commonly known as Study Bibles. That form of printed Bible brings notes from someone with access to money who can then steer crowds on how to think about what the base stories might mean.

The inspired answer is better. The inspired stories are designed to fold against other stories. Typically, there are 8 such folds as shown in the tiles tab under each aside.

If you want to know what a story means, or at least what it is like, then follow the matched tiles.

Ryan and I are just exposing the inspired system. Readers must decide how to apply. No priest gets to stand between the reader and what the text actually means.

As the grid is filling in, these pairs are exposing story meaning in amazing ways.

Future Use

Exposing asides to the URL is a nice feature. We can use this trick in other apps when it may make sense. It is possible to finally imagine a timeline app that would be built around a main timeline graphic and then use asides for dealing with dated events. This design for a timeline could then support cites from external sources like blog posts. In any case, our environment for building apps just got a whole lot more robust.

Settings

One of the important things the Story Grid is now demonstrating is how to pack more information into what appear to be individual asides. This is a very nice trick because it makes the natural complexity easier to learn.

Once we figured out how to pack more information into asides, we started to rethink our other uses of asides.

The top right menu of our scripture related apps have typically been cluttered with various asides related to formatting. These "settings" are now grouped together in a single aside. You can see this in the Story Grid app. The link above is to the Settings aside in the Story Grid app itself.

If you look through that settings aside you will see all the formatting choices that control how the text of scripture is displayed. There are also a few other settings dealing with the app itself. This includes the app's theme, and font size.

The individual settings themselves should be pretty easy to figure out. If you look at the drop down right menu you will also see it is now significantly shorter.

So once that was working, we liked it enough to want to update EVERYTHING to work the same way. All of our apps have been updated this week with at least new Settings related asides. Let me work through the list and point out other changes that are going online with this week's blog.

BRB

The link here is to the BRB. You can tap on the right top menu and see how that menu is now dramatically shorter. This should be very much easier for anyone to discover and use.

This does not (yet) have external URL access to asides. You'll need to poke around to see. The first thing to notice is the right drop down menu is very short. It has a pattern that we are using across all of our apps.

Intro

When there is some sort of written introduction, that will be in the top choice, labeled "Intro." You can see in that intro how we are using the same tricks as the Story Grid to compress a bunch of prose into an easy to use format. In the case of the BRB there are important notes on the villains.

Lots and Search

After the intro comes any app specific tools. In the case of the BRB there are Lots and Search choices in that menu.

Note that Lots now has a menu bar. That bar lists "Calculator," "History," "Info," and "Audit." This brings into 1 place materials that were spread around previously. The History was in its own aside, far from the calculator. The Info for lots was behind a circled I, the Audit was in the About. All of this is now clean and well organized and in one place.

Search works as always. We recently updated the Search system. No changes to search itself as of this week.

Settings

Then the BRB has a link to Settings. This new aside has all of the settings that are available in the app. These are generally listed in the order of their impact on the user interface of the running text.

Note that as of this week's update Ryan has been making sure that essentially all formatting in the running BRB text can be turned off. So the actual list of choices in the settings aside is longer than in the past. Beware. With great power comes great responsibility. You can now turn the BRB into something like a black-and-white printed book. How quaint.

All of this is happening in 1 aside with all the settings easily discovered just be scrolling. This is very much easier to learn. It is now easy to survey all of the available settings.

Contact

Continuing down the BRB right menu, Contact is listed next. It works as always. No particular changes this week.

About

About is the final choice in the right menu. We have intentionally moved out most of the prose that was once kept in About. There are now 3 key things kept in the About. This is now true across all of our apps.

First, there is the typical build info, like build date and revision numbers. Though not needed very often, it does have a common use. Running lots in a group requires synchronizing everyone's copy of the app to the same build number. The top of the Abound is where that number is found.

Then there is a theme verse. This is just a personal touch, like a prize for visiting this dusty corner of the app.

Finally, there is also the sharing related QR Code. This makes it easy to install the app on a friend's phone. Everyone with a phone can now hand out copies of scripture.

2026 Tabernacles

Tabernacles week starts at Sundown on Tuesday, August 4, 2026. It ends at Sundown on Tuesday, August 11, 2026.

We are planning on attempting a full read through the current draft of the Testimony across that week. Normally, a full read takes a very busy 8 days, so in common years there is not really enough time for a full read. This year is a common year, so there is not really enough time. We will likely run a day long, we'll see.

TT App

In order to be ready for that week, we have added a setting to the TT app that is called "Division." This impacts how the books in that app are divided into sections.

The default Division is based on the Patriarchs. This breaks the Testimony down into sections that follow the promises Jacob gave over his sons.

The new Division is called "Holiday" which divides the Testimony into what are ultimately 9 different reading sections. These sections are based on taking the Story Grid and grouping them into 8 major sets of 3 rows each. Revelation and Hebrews are in their own short section 9.

By flipping this setting to Holiday, the Table of Contents and the main menu in the TT app flip over to major grouping by the holiday related Story Grid rows. For the main groupings there are 3 reading sessions, so 3 rows, for each day in the holiday.

We don't yet know if there is enough time to read through at this pace. We are going to try. I will report back after that week is over on how this went.

Calendar App

The calendar app has been updated to the new Settings format. At the same time, there has been an update to a setting related to holidays.

There is a Reading section in that app's Settings. These enable read markers of various types to be placed in Calendar cells. The most commonly used Reading markers are Sabbath Reads. These show up on the calendar as SR: labels in Sabbaths. The Passover Reads and Tabernacles Reads show up on days within those annual, week long, holidays.

The Tabernacles Reads choice had been limited to the 8 day versions of those holiday weeks that show up in Sabbath and Jubilee years.

As of this week, that option now runs in all years, with day 8 after the common year holiday week normally ends. This is really only useful for hard core Testimonians. We will run with this setup over Tabernacles Week and see if we want to keep it there permanently. We may add a day 9 for the tail.

Clock

While I am on the issue of the Time apps, the clock app's Setting aside gained a much better interface for selecting the clock face. Check it out.

Updating All Other Apps

We were having so much fun with the improved interface that we then moved on and started upgrading all of our other apps. I am saying "we" but Ryan did most of the work. I was tracking down technical issues as the week progressed.

There are 13 Web Apps listed off the front of Paleo.In. All but Canon Bible were updated this week. Let me show off what was done.

Verse Reader

The Verse Reader has an updated right menu and settings are grouped.

Verse Reader Greek

The Verse Reader Greek has updated right menu and settings are grouped.

Greek Research Bible

The Greek Research Bible has updated right menu and settings are grouped.

Bible Harmony

The Bible Harmony has updated right menu and the settings are grouped.

Sabbath Reads

The Sabbath Reads has updated right menu and settings are grouped.

Qu Map

The Qu Map has updated right menu and settings are grouped.

Paleo Bible

The Paleo Bible has been updated in the same way, the right menu is updated and the settings are grouped. But, more has happened to this app this week. Let me go through the details.

Font Size Control

Earlier versions of the app did not have correct handling of Font Size. That problem is fixed this week. The Settings displays samples of the standard font sizes. The font used in the running text now actually respects those sizes. So it should be possible to see more text on screen.

Paragraphing

There is a new setting that can be used to control the type of Paragraph formatting. The current 2 choices are Block paragraphing and Verse Per Line. Paragraph placement is being shimmed in from the paragraphs used in the BRB. This is intended to allow more dense display of text on page. Apocrypha books currently have limited paragraphing.

Navigation

There is also a new setting that can be used to control the type of navigation used in the app. The 2 choices are Chapter or Story based navigation. Chapters are of course the traditional chapter breaks. Stories are a better, more natural type of navigation.

When navigation is switched to Story, the right drop down menu shows story names instead of chapter numbers. This is a much nicer system if you know your way around in the text.

Story headings have been added to the Apocrypha. Some of that is still a shim. There is still a huge amount of work to do on this app. But progress is happening.

Names

I had started to load names a couple weeks ago. Eden was the second such name. It is also a word for time. I had touched the problem and power of what will become Paleo roots. But, I also needed stronger tools for determining what English names to use with roots only when those roots are used as names. It was time for a design iteration as per the problem of loading names into the Lexicon.

I've got a plan for a much better tool chain that cross checks paleo roots against locations where those roots are used as names. Any other root like Eden should now be easy to handle. This new work flow must be done sequentially. The first occurrence of each name must be checked and entered into the lexicon. As of this week, I am currently in 1 Chronicles. This is the worst area of the text because of the abundance of rarely used names.

So names are now a large single piece of work that will go into the app all at once. So no particular updates to the interlinear data in the Paleo Bible app this week.

Because I am using an internal version of the VR app, I have visibility to all the different English used by different texts across history. Since I need to load those names into the new setup, I decided to load conventional modern English as the first round of these names. I don't intend to end there, but I could imagine conventional English might end up under a setting. I could also image more correct English names as the default view once we are past audit. So running what becomes a second set of names makes sense now. This pass does not need to be perfect.

This was a good conceptual starting point. But it soon got strange. My mental model of Biblical names was sorely inadequate for what is actually going on in the text. Let me review what I am seeing.

Trouble

I have never actually looked very closely at this problem in the past. This work has been a MAJOR learning curve on the differences between Aramaic based texts and the Hebrew/Greek/Latin/English based tradition that everybody in English already knows.

I set out to prime the system with conventional English. These names APPEAR to come from Jerome's Latin which was known before English vernacular bibles became popular.

Jerome visited Bethlehem so Jews could teach him Hebrew and he could have help making his Latin translation. This is where western Christianity broke from Orthodox Christianity. This is why the Orthodox generally consider western Christianity as a break away from the inspired tradition.

I now suspect that Jerome was a Masonic, so Zionist, plant who was intentionally breaking western Christianity away from its historical Greek roots. His club of sponsors could eventually make the text say anything they wanted. Hint: Zionism does not exist in Orthodoxy. Jerome's work was when western Europe was first defeated by Jews in the war of religions. That battle still continues against Russia, Iran, China and a few others.

So the ultimate chain from Paleo to English was via Aramaic, Hebrew, Latin and then English as it has evolved for centuries. The New Testament has no Hebrew in the chain. So the New Testament chain is something like Paleo to Aramaic to Greek to English, where English has continued to evolve. Of course the Orthodox chain does not have much Hebrew, provided they are on the Greek Old Testament.

The model I have spelled out here are mostly conventional, accepting disputes over Aramaic primacy. This is, though, some sort of imaginary chain. It does not explain everything going on in the text. There are a few other points that seem to matter to what happened across history.

Editors

So what language did the Editors use? The professor I have linked in videos seems to think there is linguistic evidence of some Hebrew to Aramaic. That would not surprise me. Editors were not writing in Paleo. So their edits were in Hebrew or Aramaic. Hebrew sources for additions would explain the clues the professor is hinting at in Aramaic.

The implication here is that the number of translations in the chain of transmission into English is now different for different passages in the text. This is not just New Testament vs. Old Testament. It is based on where edits were being made. So some passages will naturally have different problems based on their specific history.

Sound System

So there are known sound system issues through this language chain as well. Most everyone knows the Y sound in Hebrew comes out as J in Latin. Q comes out as C, K or CH. S and Sh sounds are forever messed up. Those even happened in Judges. I was prepared for these differences.

The Scripts exhibit shows these differences too. There appear to be times in history when nobody was literate in the western world. Pentecost impacted language systems across the planet, especially across the Roman world. It was a New Testament era replay of the Tower of Babel. These sound system and letter pronunciation differences can be explained through that history.

But, I am finding another sound system change. The D and R are also changing across names, as seen down across time. This one is interesting because it explains yet another interesting problem.

The Scripts exhibit that was 3d printed last year also shows digits. Most digits are just Paleo letters, in order, matched to their number. One of those digits is wrong.

The Du letter should be the basis for the drawn form for the modern digit 4. Instead we find the Re letter is the basis for the drawn form for the digit 4. Remember, R did not always have the descender. Even in English you can see the 4 and the R are mirrored but similar.

Where, or when, the chain of transmission saw the Du-Re reversal, I cannot tell. I can see that current English names will at times have changes in all of these letters. We've known roots of names like Ya-Qu-Ba in Paleo might become J-K-B in English. Now the R plays games too. Once we get to the rare names, with letters like R, the amount of changes becomes much more widespread.

Legal Translation

It has been a few years since I reviewed this point in the blog. But the modern history of translation is important to remember. When the European Union was formed, they needed to write law that meant the same thing in each national language of Europe.

This needed a set of translation skills not normally practiced. Translation of law had to mean the same thing in each national language of Europe.

This is a difficult skill. It is only taught in a few places in Europe. It has a whole family of translator tools that go with the problem. This includes careful authorship of the original laws. Translations are thus unambiguous as well. There can be no ambiguity in European law as there is in most American law. Courts in Europe don't need to define what laws mean as much as courts do in the USA.

Some of those modern tools are statistical. Accurate translations tend to exhibit similar statistical patterns as the original. This only happens because the translators are taking special care in their work. Sloppy translations, so all ancient translations, tend to have fewer unique words than the original. It was a report of those tools used against Aramaic as compared to Greek where I first learned and believed Aramaic Primacy.

Another important modern translation tool is called round-trip translation. This involves taking a base text, translating into some other language, and then having a DIFFERENT translation team, translate it back into the base language. The parlor game "telephone" is built around this same idea.

I have been using this round trip tool in my head as I have been working names for the lexicon. Let me explain this by the example I learned in school.

Example

I remember a particularly interesting session in a Master's level English class. The professor was dealing with real world problems for international advertising.

The rule taught in class was that any public writing needed to be through a round-trip translation process. This means you hire a translation from your source English into a target language. Then have someone else translate back into English. If it does not mean the same thing on the way back, you have a problem.

Importantly, both sides of that process could NOT be done by the same translators. Nor even done by the same translation service. This had to be done before any money was spent on using that translation in advertising.

The professor's best example of this problem was from a Coke campaign. "Coke Adds Life" was the phrase blasted across all media in the USA at the time. Most Americans, in the mono-culture of that time, knew the expression.

It was so popular, Coke then ran the same campaign around the world, including in South Korea. Not only did Korean sales of Coke products collapse, they started getting nasty feedback about having run such a terrible ad campaign.

Of course the Coke executives had no idea what they had done. They hired consultants to figure it out. Those consultants came back and said you spent a ton money telling Korean language speakers that "Coke brings back dead relatives from the grave."

The original phrase, "Coke adds life," does not actually mean anything in English. The translators had no idea what to do when moving the English into Korean. They guessed. But, they did not know their hack translation would be splatted across the country. To their credit, they did pick the same total number of Korean words as English words.

This is why round trip translation is important. It is turning out to be a good check of English manuscript translations. When the Aramaic, which is near Paleo, is available, does it match the English? Could the English be translated back to Paleo and mean about the same thing? I am running these questions in my head with every verse I am looking at.

Translator Care

So let me ask the question: How much care did ancient slave translators put into the task of translating additions to sacred scripture?

Did they treat their work like the translators working on European law?

Did they think they were going to have a huge audience?

Or were they just translating strange memos from the boss without much care?

Dusty Corners

I use the term "dusty corner" to indicate any area of any project which does not normally get much attention. This could be your attic. This could be at the zoo in the deer section. (Especially if you live where there are deer.) It could also be some part of the Bible that does not get attention very often by readers.

Some dusty corners should not be dusty. The last 3 chapters of Judges is a good example. Those chapters are dusty because the content and implications are scary to most readers. Some dusty corners are dusty for good reason. There are many long genealogies in the text that do not carry much weight with most readers. Who cares about who begot who? These are natural dusty corners.

Dusty Genealogies

So I have been loading names from dusty genealogies into the lexicon. In effect, I am doing a round trip translation. I start with a Paleo term. In history this was an Aramaic term. This is already once removed from a theoretically audited original Paleo text. Here soon, we will audit our way back to that layer.

So my current tooling starts with unaudited raw Paleo. I then survey down the list of intermediate translations and see some English for the ancient name.

The KJV is about the oldest English that matters because it resembles modern English. The KJV usually agrees with modern English. At least for major names. The KJV is still stacked on Jerome's work. The KJV era names, especially for the major, common names, are the names everyone knows in English. For uncommon names, like in dusty genealogies, there is more strange stuff going on.

Very new translations, like the NIV, are often diverging even more than the KJV.

The joke when I was young was the NIV is the "Not Inspired Version." No kidding. The NIV is picking up recent changes in the Hebrew texts from the past 100+ years. No one ever told me the NIV was based on a modern edit of the Old Testament. This is a dirty little Zionist secret.

In any case, there are many places in the text where there are dusty corner verses, which do not get much attention, which do not even remotely round trip back down to Paleo.

This can be caused by sound system changes. I explained that above. Those are not that serious. This can also be caused by modern editing, say the OT Hebrew used by the Zionists building the NIV.

These changes can also be caused by careless translations somewhere along the historical translation stack. These were not modern legal high-skill translators. At times they were doing rough paraphrases. It is not unusual to find verses with strangely different order in the various phrases that make up the verse. These are things I never expected to see.

More Later

I have been moving fast for time. I do have about 2300 names to enter. So I am not taking notes. I am not trying to collect evidence. Once the tooling is done there will be ample ability to come along later and study this problem more completely.

But I am using this blog to record what I am seeing. We will return to this topic again in the future.

War News

This week we were not particularly looking for any change in status with the war in Iran nor the war in Ukraine. The Friday this blog goes out is a possible shift related to Noah, so perhaps something with the Iran war. We are basically approaching 150 days from the start of the war. I will return to this date if needed in next week's blog.

There has been considerable reporting from sources in Pakistan dealing with the Trump administration itself. The short story here is that Trump appears to be unable to stop the Zionist war against Iran. Trump appears to have been tasked to get a cease fire. This, presumably, to give the Zionists time to re-arm.

The Iranians have answered Trump with requests to do the agreed upon items from the MoU. This is presumably a real test on whether Trump is able to carry out any executive branch function of the American government. Trump appears unable to carry out anything agreed to in the MoU. Someone else is running the USA. Some of the people around Trump are probably minders, set there to control everything Trump says or does.

So the USA continues to bomb Iran. Iran then continues to bomb American military targets around the Persian Gulf. Unless the Zionist side escalates in some way, Iran appears able to slowly remove all American bases from the region.

Many American assets have been moved to Israel. This is some distance from Iran compared to, say, Kuwait. Iranian's have the missile capacity to strike Israel. But, Iran appears to be "sweeping the room" of Americans starting from the east.

Yemen

The Ansarallah government in Yemen has now closed the south end of the Red Sea to ship traffic related to Saudi Arabia. Other ship traffic is free to pass. This blockade adds many weeks of shipping time for oil from Saudi Arabia to reach Asia. This time delay is because that traffic must go around Africa via the Suez canal. This also limits maximum ship size as super tankers cannot fit through the canal.

This closure changes the cost equations for Saudi oil. It should give the Europeans a chance to out-bid Asia for some of that oil.

Just a note on the proper name. Western media uses the term "Houthi" to denigrate the leaders in south Yemen. Houthi is the name of one of the major families in that region.

The use of the Houthi term implies south Yemen does not have a legitimate government. That government's actual name is Ansarallah. Because western media refuses to use the correct name, there are 3 different English spellings in common use. Ansar Allah, Ansarallah and Ansarullah are all used in different places. Presumably one such spelling will settle out over time. I am using the compounding of Ansar and Allah. This seems the most respectful of the 3 different common forms.

I will attempt to use their correct name in blogs going forward. If "Houthi" was the correct term, then the drone videos of massive rallies in Yemen would suggest the Houthi family has maybe 2,000,000 members.

Since the American government is occupied by Zionists in similar fashion, perhaps we should pick a denigrating name for the American government. How about Last Trumpers?

Watch Dates

Theoretically, we have a possible funeral or death or some similar headline for a northern king on 2026-07-26, which is the Sunday after this blog goes out. Weekend dates usually see headlines pushed off to adjoining days.

This will presumably fulfill with the Graham funeral. Preparations should begin on Monday, with formal ceremonies in DC on Tuesday. State level ceremonies are on Wednesday. But, note, there is quite a bit of heavy western hardware moving towards Iran for a possible strike over the weekend. Another attempt at defeating Iran might be the fulfillment headline. The Jewish work week in Israel begins on Sunday, which for them is a fine day to start a war.

Peeking ahead, we have a possible minor Noah date on 2026-08-07 which should see something around Iran. We reach the replay of the end of Amaziah's reign on 2026-08-11.

Headline Review

The following caught my attention this week.

Note, I have recently learned that X does not let inbound links render for non-subscribers. I don't know if this is always true, but it seems to be. For now, I will still keep using a few X links.

Link rot is also a thing. The best long term answer is to keep screen shots in our own systems. That is a work flow and blog change that likely comes with a timeline app. If someone has a better solution, please let me know.

War Graphic

The link here is to a Zionist prepared graphic of ground invasion war plans in order to conquer Iran. Art is easy. War is not. Barring use of nuclear weapons, the advantage is still with Iran.

Nuke Plans

The link here is to a long form article on SGT Report dealing with post 911 nuclear war doctrine changes. Small nukes have been used by the USA in various places in the modern era. Iraq is thought to be one of those places. (Lebanon and Syria are others.)

This article is being linked from current social media posts with commentary on the idea that the Zionists are planning a nuclear war against Iran using small scale nukes. Resorting to nukes is the escalation strategy for anyone loosing modern wars. It is the USA war doctrine to do so.

These weapons drop the cost of war considerably. As the USA becomes dirt poor, these weapons will become popular. Even inside the USA.

Nuke's For Saudi Arabia

The link here is to a Zero Hedge article dealing with Trump granting nuclear tech to Saudi Arabia. This is said to be for commercial nuclear based energy.

This for the country with more fuel than nearly any other place on earth. This also for a country which is mostly sandy, sunny, desert. This is an deal place for solar panels, not nuclear energy. Fat chance this agreement is really for energy related uses.

Most social media commentary says this is to cover for granting the Saudi's their own nuclear weapons. We are heading towards nuclear war.

Press TV, Saudi Nuke Deal

More on the same Saudi Nuke deal. The issue is proliferation of nuclear weapons. Everyone knows this. Trump is a fool to not admit it. They want the Saudi's to nuke Iran so Russia and China do not nuke the USA in retaliation for the USA nuking Iran.

Rubio and Lavrov

There was a high level meeting between Russia's Lavrov and America's Rubio during a larger conference in Asia. The link here is to a Zero Hedge article with a few details.

The media people asking questions were following war news reality based on social media, unlike the media crew at the White House. Rubio goes meta.

The Zionists cannot stop conquering Russia. It is their religious goal.

The other way to think of this meeting is Lavrov is the cat. Rubio is the mouse. Maybe this should be this week's cat video?

Tass: Rubio and Lavrov

The link here is to the TASS summary of the same meeting. Tass is a class act. Rubio says there is much work to do in order to end the conflict in Ukraine. Why? I can answer that. Rubio still has much work to do in order conquer Russia. Only that will end the war in the minds of the Zionists.

Ukraine Collapse

The link here is to a post on telegram with the population statistics of Ukraine. For those old enough to remember, the death/birth ratio in Ukraine is now nearly the same as the Khmer Rouge in Cambodia in 1976 and worse than the Rwandan Civil War/Genocide. This part of Europe is now worse than anywhere in the 3rd world. Thank the Zionists for making Europe 3rd world.

More Later,

Phil