Long Term Headlines
This week we did a major UI update to the bibletime.com website. It is still missing charts. This caused me to think about long term headlines. Covid is perhaps the best current example. This blog explores what we did to bibletime.com and then explores these issues with an interesting example of the problem.
Voron Status
I have been pacing myself through the new Voron build. The kit requires 3d printing for all of the plastic parts in ABS plastic. That type of plastic needs an enclosure. So I am using a cardboard box around one of the other printers to print those parts. So they are coming out sequentially. The last parts rolled out earlier this week.
I am waiting until I see what the Voron can do before resuming design work on Tabernacles items. I sketched out the new ezekielsbones.org website to this end, but that caused me to want some design changes to how we do websites.
Ryan and I spent about 10 days working on the build environment and the styles that will get used on ezekielsbones.org, but we started by applying them to bibletime.com. That website is much larger and it hits most of the situations that we would expect in other sites going forward. Here is the link to our updated version.
Bible Time (bibletime.com)
This website was first online in late 1998. It remained my personal focus until after we moved to Idaho in 2004. It has remained online ever since, but it has not had much attention given everything else going on around here.
We went to the Internet Archive and pulled up a version from early 2004. This was just before our mid 2004 move to Idaho. We needed a reminder of the original look and feel of that website.
In that era the website had to do server side rendering for every page request. Microsoft's Internet Explorer caused hell for all web developers. That code was written in .php, itself a lesser form of hell. That code would get migrated to python, still trouble, and then eventually to the current Javascript.
Curiously, those shifts in languages were driven by explicit prophetic from Joshua. He did not like using certain languages and he did not like using different languages, thus the eventual move to Javascript everywhere.
Page rendering was eventually done in our build environment, making our server environment much more secure and fast. Javascript is a required language for some code in the browser, so running Javascript everywhere made my programming life much easier. Of course Javascript itself has radically changed over the years. Modern Javascript is written much different than Javascript even 10 years ago.
2004
Looking again at the 2004 version of the site was a throwback to an earlier era. Web browsers of the time were crude, and things like rounded corner tabs were almost impossible to build. Nearly every feature was built on hacks against Internet Explorer. That dreaded piece of garbage has been gone from the Internet for some time now.
For those that might care, here are some of the worst examples from those days. To round the corners on tabs required floating images into the corners of those tabs. To color the trim on tables required a table tag inside another table tag. The outer table tag's color set the trim color of the inner tag. Such was the strangeness of HTML in those days.
So the technical world of 2004 was horrible to work in. But that 2004 era website style was attempting to maximize discoverability. That strange technical term is something we have lost track of with our focus on web apps.
A highly discoverable site means someone visiting the site for the first time would immediately have a good sense of the scope of the content of the website. They would also be able to easily explore and find new and interesting content. They would have reason to stick around and learn.
I tracked that stuff closely by watching how long random visitors spent on the site. Different UI changes had very dramatic impacts on total time reading pages on the site itself. By 2004 it was tuned to keep visitors reading.
All of this history came flooding back when we looked at that 2004 era archived version. After we looked at that old version, both of us decided we needed to restore as much of the design we were using at the time as we could.
Of course in this refresh we are using all the latest underlying tech. Grid layouts in style sheets are a good example. This lets the site easily cope with small phones and large format 4K displays.
In terms of appearance, bibletime.com is looking better now than it has in many years. It is now as discoverable as it has ever been. Even with what some will call a retro-2004 color scheme, which we have also recovered for old times sake. We hope future visitors to that site will have as much fun as they did in 2004, when the internet was young and interesting content could be found.
Charts
In the 2004 era there was a technology called .jnlp files. These allowed websites to include desktop java based applications. Click the link on one of those pages and a desktop app written in write-once, run anywhere, pure Java, would automatically download and launch.
The Bible Time charts were handled using that technology. Until, of course, some fool somewhere in the industry decided to drop support for that tech in web browsers.
I am sure someone managing the national propaganda narratives did not want to loose control of desktops to the wild internet. The fools who run Apple still don't want to let average people install anything to their phones, thus fights in Europe over web app tech that Apple limits worldwide.
At some point I still want to restore that jnlp style chart functionality. My work load does not allow it to happen now. The tech will be web apps, Javascript, html and css, the same fundamental tools as we already use every day.
That huge chart has some small cousins. These have always been embedded inside individual pages. These need to be recovered too. I did the first of those charts as part of refreshing the general UI this past 2 weeks. Here is the link.
Passion Chart (bibletime.com)
The passion week chart page linked here was perhaps the most visited page on the site. It captures all the timed references to events in Passion Week and lays them out on a graph. It is really good to see it back and running again. You can check the results yourself to see how it turned out.
Graphing General Headlines
Some recent headlines have caused me to stop and think about how best to graph them on a timeline style canvas. The problem is some headlines spread across time. The decision taken in 1975 to limit world population to 8 billion people is but a recent good example. We did not learn about it for 50 years, but it ties back to key events on the chart.
911 was another similarly strange headline date. Reporting that day was very much incomplete. Later we learned about the groups of cars mysteriously exploding and burning along the Hudson and East rivers. Later we learned about how Earth's magnetic north pole moved towards NYC that day. Those details all came out later when others went to research what happened.
Of course the media at the time could cover the news that day in real time. That media does not exist anymore either. When Tucker was on Fox news, his audience's median age was 74. So half of his audience was over 74 years of age. For every one of those elderly viewers there was only 1 other viewer under 74 years of age.
Most young people have no interest nor ready access to network TV. So a similar headline these days would be hard to find while it was going on.
Actually, 911 was hard for us to see in real time too. The cabin where we lived was in the foothills of Mount Hood in Oregon. It was without any TV. Internet was only dial up. I remember driving to a friend's house 30 miles away to watch 911 on live TV.
The Bible Time charts were based on citations to various written sources. From the print media world this meant references to page cites in printed sources. This does not exist any longer. Most news sites are now online with no block chain support. The newspaper world was block chained, so there was no way to change the record of history like there is now. This is a big issue that I will return to in a future blog.
For the purposes of Time Line Charts, these problems can be worked out, but they are new problems. Rebuilding the charts means rethinking how to gather source material and citations.
There is another type of problem, headlines like we have tracked here with Covid. Here is a link to a recent article on Nursing Home deaths. Let me deal with the contents and then return to the problem of tracking this sort of thing on any sort of future charts.
Nursing Home Data (kirschsubstack.com)
This article is by Steve Kirsch. It is long and an important read. In the article he uses publicly available data that tracks all known nursing home deaths in the USA. He is qualified in statistical techniques, so he is an independent expert, not working for the government. He set out to see for himself if vaccines are the cause of Covid related deaths.
Kirsch draws several conclusions. The first is that the vaccine itself starting killing people as soon as it was administered across the USA starting very early in 2021. He also shows in several different ways that the vaccine itself is the cause of death, not any supposed virus. He also shows that this is a continuing problem, death rates remain elevated in the vaccinated public in the USA.
We know from personal testimony from readers of this blog that all death related industries in the USA are still running at above normal capacity. Not everyone working in these businesses wants to talk publicly about what they know. But, let me return to Kirsh's article.
Call For Prosecution
Kirsch also calls for the criminal prosecution of certain nursing home and other medical staff involved in administering vaccines. I have not seen this call to action before. He is not calling for all such staff to be prosecuted, but a few in very specific circumstances. Let me explain.
Not all vaccine batches were the same. We have known this from other sources for years. This is why we think it is a population control system.
But Kirsh points out that some batches were very, very, very deadly. Some vaccine batches killed instantly everyone who got a shot from those batches. This is news. Kirsh has the data to prove it. His data good enough to use as evidence in court. Kirsch also knows from the public data the exact addresses of nursing homes where this was going on.
It looks to me this is the Nixon era planned population cull going on. Someone intentionally changed death rates by zip code. They set out to limit world population to 8 billion people. They had a geographic agenda, at least. But, back to the story.
Medical staff administering these deadly batches knew that everyone getting the shot was dead within a day or so of getting injected. In nursing homes, especially, the staff tracked every resident and knew exactly what was going on with each person.
Those nursing staff who later did a second round of shots are criminally liable based on their medical code of conduct which precludes knowingly killing people.
The first round of vaccine deaths in their facilities was enough to trigger their professional responsibilities to stop administering the vaccines at all. This is where they became criminally responsible.
Kirsch suggests in the article that he is looking for these special cases, and may file criminal complaints himself.
My opinion, and why the article above is so interesting, is that a few such cases with wide publicity would stop this from happening for another generation. Medical staff going to jail for following orders to kill people might stop others from doing the same.
A few cases like this might change the culture. Just like not drinking certain beer, nor shopping in certain chain retailers, is changing the culture for the better.
Getting through the prophetic dates of 2029 requires stuff like this to happen widely.
How To Chart
So how does research like this go onto any sort of future prophetic timeline chart? These do not appear to be date/point headlines. They need some place to carry the narrative that is supported by date headlines and the prophetic stories behind them.
This becomes a complicated User Interface problem. There are point dates and also prophetic stories that spread across time. Then there is a need for deep dive articles that explain how these things worked out in the years following. It is a complicated problem that needs a User Interface that is discoverable.
In any case, these are the headlines that will define daily life for all of us for decades to come.
More Later,
Phil