Zuckerberg should Should be Arrested Right Now!


Armstrong Economics Blog/Opinion Re-Posted Jan 2, 2021 by Martin Armstrong

We are now dealing with Facebook is deliberately interfering in elections. They shut down the page for Republicans raising money in Georgia 2 days before the election claiming they violated their community guidelines. I am sorry, but Zuckerberg should be dragged out in chains. He is now violating everyone’s civil rights in the nation. They wanted to start a war by claiming Russia interfered in the US elections and Congress demanded sanctions.  Facebook is acting far worse than the Russians were ever accused of.

We need a special prosecutor to be appointed right NOW to criminally charge those in BigTech deliberately trying to manipulate the election. These dropouts obviously view that the US Constitution violates its community guidelines. Enough is enough! They should now be locked up.

What About Fake News?


Armstrong Economics Blog/Politics Re-Posted Dec 15, 2020 by Martin Armstrong

The question dealing with the press is not something new. Matthew Lyon was the first person to be put on trial for violating the Alien and Sedition Acts of 1798, after publishing criticism of President John Adams. The Sedition Act of 1798 criminalized the “writing, printing, uttering or publishing [of] any false, scandalous and malicious writing or writings about the government of the United States.” Indeed, Trump could have and should have charged people from the media who clearly violated that Act. Lyon was sentenced to four months in jail. While imprisoned, he was elected to represent Vermont in Congress.

It was actually Abraham Lincoln who seized the telegraph lines and issued an order prohibiting the printing of war news about military movements without approval. He was censoring the news back then for anyone who challenged his administration. Lincoln had people arrested for wearing Confederate buttons and for singing Confederate songs in the North. He went as far as to shut down the Chicago Times for criticizing the Lincoln administration. The editors were arrested, the newspapers were shut down, and the journalists were banned from the fields of battle. A military governor with the approval of the secretary of war, Edwin M. Stanton, destroyed the office of the Sunday Chronicle, a Washington, D.C., newspaper. Lincoln even had a Democrat member of Congress arrested for making an anti-war speech in his home state.

In April 1863, General Ambrose Burnside, who was the commander of the Department of the Ohio, issued General Order No. 38. Burnside placed his headquarters in Cincinnati to intimidate Confederate sympathizers. He issued General Order No. 38.

General Order No. 38 stated:

The habit of declaring sympathy for the enemy will not be allowed in this department. Persons committing such offenses will be at once arrested with a view of being tried. . .or sent beyond our lines into the lines of their friends. It must be understood that treason, expressed or implied, will not be tolerated in this department.

Burnside also declared that, in certain cases, violations of General Order No. 38 could result in death. Most could not believe the audacity of this order which violated free speech. Clement Laird Vallandigham (1820–1871) was so opposed to the order that he allegedly said that he “despised it, spit upon it, trampled it under his feet.” He also allegedly encouraged open resistance to Burnside. Vallandigham was said to have criticized President Lincoln for not seeking a peaceable and immediate end to the Civil War and for allowing General Burnside to ignore the constitutional rights of citizen’s. It was reported that Vallandigham had violated General Order No. 38. The general ordered his immediate arrest. On May 5, 1863, a company of soldiers arrested Vallandigham at his home in Dayton and brought him to Cincinnati to stand trial.

Burnside charged Vallandigham with the following crimes:

Publicly expressing, in violation of General Orders No. 38, from Head-quarters Department of Ohio, sympathy for those in arms against the Government of the United States, and declaring disloyal sentiments and opinions, with the object and purpose of weakening the power of the Government in its efforts to suppress an unlawful rebellion.

Vallandigham was tried by a military tribunal and was found guilty despite his argument that they lacked jurisdiction over a civilian. The tribunal sentenced him to remain in a United States prison for the remainder of the war. Fear that this would result in a rebellion after he appealed to a federal circuit court. But the court, corrupt as it was being pro-government, denied the appeal. Judge Leavitt held that General Burnside had military authority which was necessary during a time of war. President Lincoln feared that a rebellion would erupt and commuted Vallandigham’s sentence to exile in the Confederacy. On May 25, Burnside sent Vallandigham into Confederate lines.

Then in 1917, Rose Pastor Stokes, who was an anti-war activist, writer, and a founding member of the American Communist Party, was prosecuted under the Espionage Act of 1917 for writing to a newspaper: “I am for the people and the government is for the profiteers.” The Act criminalized attempting to cause insubordination to the war effort, willfully attempting to cause insurrection, and obstructing the recruiting or enlistment of potential volunteers.  After being sentenced to 10 years in Missouri State prison, she successfully appealed to the US Court in St Paul. The government ultimately dismissed the case against her in 1920.

Therefore, many people have written in asking if CNN, New York Times and the Washington Post could ever be shut down or their editors prosecuted for supporting Klau Schwab and his take over of the world to push it into Marxism. There is plenty of precedent for that. Trump was never advised properly and the Department of Justice would never investigate.

CTH 2.0 Updates, New Comment Platform Initiated


Posted originally on The Conservative Tree House on December 8, 2020 by Sundance

As you can see CTH 2.0 is launching a new comment platform to improve the features and user engagement we have all come to appreciate.  Here is some background information about this comment process that will likely answer questions.  Please book-mark this post and share it for those who do not read the site updates and just go into the comments.

Because we are free from the constraints of WP/Automattic we are able to explore features that many Treepers have asked for.  We have selected comment software from WPDiscuz (not affiliated with Disqus in any form) specifically because we can control the platforms internal content according to our privacy demands.

No outside system is gathering any user data or content on the commenting platform, everything within CTH 2.0 is being built on a very stable and private proprietary foundation.

The ability to add videos, graphics, pictures, tweets, scribd embeds and other functions is now present in the comment section.  This is called “Oembeds”, and it is live right now. However, we will not be activating a feature that allows you to upload images or videos directly from your computer.  If the image/video has a url, it should be visible.

There are other features we will likely add to the comments section, but we must go painstakingly slow, and here’s why….

At each step in the process of adding features we have to pause and measure the impact on server capacity to support the addition.  Each feature creates a small amount of data that communicates with the servers in real time (ie. the bandwidth).  Think of it like a pipe, and each feature adds data into the pipeline… the pipe has a capacity… we add, then evaluate, ensure pipe capability/stability, then move on.  The issue is scale.

CTH 2.0 is a massive community of simultaneous users.  Each user engagement requires a live-time upload of data from server to you.  The page load time is directly related to the bandwidth capacity… if there are a lot of simultaneous users the level of data transfer can overwhelm the pipe…. it can clog and freeze.

Additionally, each new feature creates a draw from the server capacity at the end of the pipeline.  For lack of a better explanation this is the CDN rate.  CDN = Content Delivery Network.  CTH 2.0 is a massive load of data that updates for each user as they land on the homepage and visit the articles.  Again, it is a matter of scale.  As we said before CTH is a community, essentially a social media platform, working inside a website.

Our community engagement, the size of our commenting community, exceeds almost all other types of websites except for social media sites.  Those sites are specifically designed for community engagement… CTH 2.0 is leading the charge back to the era before Big Tech took control of content delivered to you.

The content in the community (the comment section) is derived from your choices, your freedom.  It is your discussion and we are stewards protecting your conversation.

With 5,000 simultaneous users on-site at any given moment, the bandwidth demand is large.  With 100,000+ unique daily users and 500,000 page views per day, the data load (CDN rate) on the servers is large.   We are chewing up about 5 terabytes of server space per day even with two cache services hosting the older content.  We always knew our data load was heavy, we just didn’t know how heavy.  This is why almost all other suggested solutions for our CTH 2.0 launch would not work.  It is a scale issue.

All of these are essentially good problems.  The rebel alliance is strong and the assembly is large.  We just need to consider that each small 4gb feature addition for a single user has a magnitude of impact based on the scale of our assembly.

Think about walking into a bar with 100,000 friends and everyone orders one drink at the same time.  The bartenders (servers) are going to get overwhelmed pretty quick, and the beer kegs will run dry fast.  Then think about everyone ordering two drinks. That’s the type of scale issue we are navigating while keeping the bar open.

With all that in mind we initiated the new comment system with Oembed functions activated.  Now we watch a little while and make sure the pipes (bandwidth) and servers (CDN rate) can handle the data load.

Then we add the “likes feature”, and we watch again… we keep repeating this process with every feature until we have safely checked-off our priority list.  There are a lot of features we want to provide while at the same time the server host is trying to figure out what the level of our site demand actually is.  Again, good problems, but this is unknown territory.

So the proprietary comment platform we have selected is stable, private and secure.  It also allows us to add features that you have requested.  We just need to measure the impact of each addition as we move along.

Also, CTH is modeled on an eleven year-old platform theme. It is reliable, but it is also clunky, heavy and not as streamline as modern tech can provide. As described, CTH is a heavy data-tank on a highway with the ability to collapse the road. We need to modernize and get faster while retaining the depth and purposeful mission priority.

We need to change our theme platform to be responsive to the type of device you are using making it easier to navigate the site from phones and iPad type devices. The engineers are working on a proposal, and a test site is experimenting. The good news is our site content is not complex and the modernization should not be too difficult. In essence, CTH presents itself differently, more user friendly, depending on the type of device you are using.

Additionally, one of our priorities right now is establishing an email notification system where you can subscribe to automatic notifications of new posts etc.  As with almost all systems of this type (there are many) it involves the use of a third party email transmission process. Y’all are aware that privacy is a CTH priority, so we are being very careful about vetting the service and setting up this notification system to protect CTH users.

CTH does not compile user information, does not engage in the manufacture of processes that assemble lists of users or any user data. We are working to ensure we do not end up creating an external list of subscribers that would be vulnerable to exploitation.  Your privacy in all matters related to CTH engagement is my priority.  This new commenting platform can also deliver that type of email notification service, we are evaluating.

Thanks again for bearing with us as we work through some technical issues, search for optimal solutions, and fiercely retain the original values and mission priority of the Treehouse.  The Truth Has No Agenda

Myself and the incredibly hardworking site admins consider ourselves stewards to this community. YOU are what matters.  Your ability to analyze, discuss, crowdsource and provide your comments on the subject matter is what makes CTH home. We will NEVER remove a commenting function from our website.

In fact, it is the crowd-sourcing work we have done as a community that has been the most thrilling and brilliant part of our work together. I will never lose that focus.  The key to Treehouse 2.0 is recognizing we have built something within a big tech ecosphere that wants to see us removed.  By being proactive we have avoided some serious challenges and that makes us better stewards for our conversation.

Remember, YOU are the important part.

Without you CTH doesn’t really have a purpose.  Individually we could stand outside shouting at trees with no impact; but together, sitting on the figurative cyber-porch, the conversation is rich with unique skill-sets, subject matter experts and life-long experiences that make discussion so much more valuable. Myself and the CTH admin team cherish the value you represent.

Please share your feedback and suggestions on the comment platform.  Does it work for you?  What do you like or not like about it.  We will modify, when possible, based on feedback.

Love to all,

~ Sundance

Site Updates, CTH 2.0 Priorities, and User Experience Feedback Requests


Posted originally on The Conservative tree house on December 4, 2020 by Sundance

As we work through bugs associated with CTH 2.0 launch, consider this a thread to provide information, report user issues, ideas and concerns. Please read the information provided below as it might answer many questions in advance.

Again, my sincere apologies for any site disruption and/or user issues you may have encountered or might be continuing to encounter as we level the ship.

The majority of major site issues have been reconciled over the past 36 hrs.  CTH 2.0 is flying even and stable.

The DNS issues are resolved, and all inbound links to TheConservativeTreehouse.Com should now be landing on the correct and most recent homepage.   There was an issue with dual cache conflict between our new server host and a mid-way cache service intended to assist with the overall site demand.  That was causing older pages to propagate upon user entry. That problem has been resolved.

Given the short time-window we were operating with; and considering the objective of Big Tech Automattic to disrupt an ongoing conversation adverse to their interests; we succeeded in keeping the CTH community voice in the fight.  Trust me, this was no small effort to achieve and is cause for much appreciation and celebration in the big picture.

The rebel alliance is alive, well and we have made new ‘rag tag’ misfit friends.  Your support was/is critical in achieving that objective.  We are humbled and thankful.

Now that we have an essentially fully-functioning architecture in place, we are able to start a slow and methodical process to enhance the features most important to our community.

Each feature must be installed, applied and evaluated for downstream issues. It is a painstaking process and takes a little time to ensure we don’t attach a feature that creates an imbalance or impact upon the essential functions of the site.

CTH is modeled on an eleven year-old platform theme.  It is reliable, but it is also clunky, heavy and not as streamline as modern tech can provide.  As described, CTH is a heavy data-tank on a highway with the ability to collapse the road.  We need to modernize and get faster while retaining the depth and purposeful mission priority.

To the details:

♦ 50% of site traffic comes from desktop/laptop computer use, and 50% comes from mobile devices (phones, pads etc).  This is one of the issues with our older theme still in place, and a team is working on it right now.   When CTH first launched mobile platforms were in their infancy, in the modern era mobile devices are now the norm.

We need to change our theme platform to be responsive to the type of device you are using making it easier to navigate the site from phones and iPad type devices.  The engineers are working on a proposal, and a test site is experimenting.   The good news is our site content is not complex and the modernization should not be too difficult.  In essence, CTH presents itself differently, more user friendly, depending on the type of device you are using.

♦ One of our priorities right now is establishing an email notification system where you can subscribe to automatic notifications of new posts etc.  As with almost all systems of this type (there are many) it involves the use of a third party email transmission process. Y’all are aware that privacy is a CTH priority, so we are being very careful about vetting the service and setting up this notification system to protect CTH users.

CTH does not compile user information, does not engage in the manufacture of processes that assemble lists of users or any user data. We are working to ensure we do not end up creating an external list of subscribers that would be vulnerable to exploitation.  Your privacy in all matters related to CTH engagement is my priority.

♦ Next, we are working on a return of the “like comments” feature in some manner or form. The issue with a like feature is a direct all-time link between the user engagement and the host server.  In essence, to have a “like feature” there is a continual feed every millisecond attached to the server.  That is ok, but as with all things in tech world can create a draw -own of site performance given the scale of our assembly.

Don’t worry about “likes” being off-the-table, they are not.  This function is actually important to me, and we will restore them because that engagement is actually a precursor to something else, something unique, that I want to see on the site.  A sidebar on the page drawing attention to the top ten highest-rated comments in a real time feed.  You click on the user name, or perhaps the avatar, and it takes you to the comment.

♦ Another new feature I want to execute is a “most liked articles” widget.  Similar to most liked comments, this would be a real-time propagated graphic showing the articles that users are most following or reading on other sites.   Instead of me aggregating the information and/or directing attention to interesting external articles, this awesome community of smart commentators can do that themselves.

In essence, you share links to important external articles or content in the comments, and the top five articles (as clicked/read by commentators) automatically shows up in this sidebar feature: “Hot Topics and Articles.”   [This is a little challenging, but the technology exists to accomplish it.]

♦ The team is also working on restoring a system that will allow embed pictures, tweets and videos to populate in the comments section.  This is a process/system called “OEmbed Comments”.  We needed to reconcile the scale of server use/demand by the commenting system before we could contemplate this feature.

Now that we have a dual library system in place for the 7.5 million comments, we can start the process of evaluating server capacity for OEmbed functions.  It is not a matter of “if” this will happen, it is simply a matter of when those functions return.

When you write a comment it creates a metadata file. Each comment is a unique url.  Your unique id is part of that metadata, your gravatar or avatar is part of that metadata, the content of your comment (what you write) is part of that metadata and any article links, citations, pictures, gifs, or tweets -each carrying a unique url- is part of that metadata.

The average number of lines of unique metadata in one comment is six to ten lines of code, regardless of the length of your comment.  Your comment creates a mini data-file with its own unique id (the url).  The library of pre-existing comments was 7.2 million.  Multiply that by the lines of metadata and you get well over 40 million lines of code in the pre-existing comment file alone. (more)

Again, it is important to remember much of this server capacity exploration is in uncharted territory on a non-social-media platform.  Fortunately, we have the ability to scale-up; our server hosts are just trying to figure out the actual scale we need.

Thanks again for bearing with us as we work through some technical issues, search for optimal solutions, and fiercely retain the original values and mission priority of the Treehouse.  The Truth Has No Agenda

Myself and the incredibly hardworking site admins consider ourselves stewards to this community. YOU are what matters.  Your ability to analyze, discuss and provide your comments on the subject matter is what makes CTH home. We will NEVER remove a commenting function from our website.

In fact, it is the crowd-sourcing work we have done as a community that has been the most thrilling and brilliant part of our work together. I will never lose that focus.  The key to Treehouse 2.0 is recognizing we have built something within a system that wants to see us removed.  By being proactive we have avoided some serious challenges and that makes us better stewards for our conversation.

Remember, YOU are the important part.

Without you CTH doesn’t really have a purpose.  Individually we could stand outside shouting at trees with no impact; but together, sitting on the figurative cyber-porch, the conversation is rich with unique skill-sets, subject matter experts and life-long experiences that make discussion so much more valuable. Myself and the CTH admin team cherish the value you represent.

♦ Taking all of the above into consideration, if you are still experiencing issues with the site in general or specific terms, feel free to drop your feedback in the comments and we will review to see of we can intercept and/or correct any issues.

Love to all,

~ Sundance

Try to avoid a fight.  Never be the first one to start a fight.  However, when it does come down to the fighting, you need to fight like the third monkey on the ramp to Noah’s ark…

…and brother, it’s raining !

Interview in Canada Censored by YouTube


Armstrong Economics Blog/Censorship Posted Dec 4, 2020 by Martin Armstrong

I did an interview in Canada with Laura-Lynn Tyler Thompson and it was censored by YouTube because the information violated their political agenda. Subtracting the total deaths in nursing homes shows that the actual number of deaths in Canada from COVID was only 165. They really will not tolerate any interview against their pandemic agenda.

CTH 2.0 Site Maintenance Complete – Mission Accomplished…


Posted originally on The Conservative Tree house on December 1, 2020 by Sundance

Data Engineers Have Optimal Solution To Restore Comment Function:

Success !!

It appears we have a workable solution achieved.  Excellent….

….Welcome Back Gang… let’s test drive this thing.

Run it hard, use this thread to try out the stuff you are familiar doing. Let’s see what we need to tweek modify or adjust to get back to peak operational condition.  Share your issues and ideas in comments.

We are no longer on Automattic/WordPress servers and despite the extremely tight forced eviction timeline we have achieved a safe rebuild ten hours ahead of deadline.  Quite an accomplishment considering the scale of the task at hand, and a holiday in the middle of it.

There are a few random reports of regional DNS issues and here’s a few tips we are discovering from users:

♦ Make sure you are using the latest version of your browser software.   Reports of Mac not reaching through to new site, but when OS “Big Sur” is added things improve.

♦ Make sure your cookies and cache are not returning you to old site activity.  I apologize for this issue because clearing your browsing history is always a mess and can often require you to re-enter all saved passwords, but that’s one of the unavoidable issues with an entirely new set of servers and new DNS targeting.

♦ All regional Internet Service Providers (ISP’s), responses for queries and bookmarks launched by users, should be aimed toward our new servers now.  Some of them took a long time to update, and there is a familiar pattern to it (discussion for another day).

♦ Remember, while we are using WordPress open source code/software, we are not operating inside the WordPress/Automattic platform.  Some proprietary functions of WP/Automattic will not be available.  I think the notification bell is one of those functions.

♦ There will be a new email-notification program initiated later today that will allow you to sign up for email notifications of new articles and updates. [In the works] In the interim Twitter users can use the notification function and all articles will cross-post to Twitter.

There are going to be features and site enhancements to come along later.  Right now the priority was to keep everything as identical and familiar as possible.  We will likely be doing some cool site changes now that we have full proprietary control and ownership of the site.

Thanks again for bearing with us as we work through some technical issues, search for optimal solutions, and fiercely retain the original values and mission priority of the Treehouse.  The Truth Has No Agenda

Please be patient if you get hung up in a moderation cue. It may take time to release some comments if they are hung up in moderation. The site admins do a great job with comment moderation and release so it shouldn’t be too much of an issue; and quite frankly, there are likely to be benefits from not having WordPress/Automattic software filtering through the comments as they post. Spam removal will be a priority.

Thank you for your support and fellowship. We will always work diligently to deserve it.

As word spreads… the voices of the rebel alliance are arriving now.  The best open-source researchers in the world are firing up their laptops and preparing for the most critical moments in the battle to save our nation.   The CTH printing presses are rebuilt, oiled,  and the deep rumble of the machinery is slowly building to a deafening roar.

We are extraordinarily thankful… and itching to get FREE VOICES back into this fight.

Love to all,

~ Sundance

Mainstream Media Remains in Denial About Voter Fraud


Armstrong Economics Blog/Politics Re-Posted Dec 1, 2020 by Martin Armstrong

Democrats are like zebra, they change their stripes according to self-interest whereas the Republicans can become white elephants when required. In this case, the mainstream media and governors swear the vote was real. However, Biden received more votes in only the swing states, beating Obama and Hillary, which is really astonishing. But the truth has been that people have been warning for a very long time that the American voting machines have been vulnerable and nobody has addressed the issue. In fact, the American voting system VIOLATES the Equal Protection Clause because there is absolutely no standard nationally for a federal election. In some states, anyone charged with any crime loses their right to vote and the governor has to restore it while in other states they can vote. This is no different than saying people of color are not allowed to vote in some states or anyone who belongs to a particular religion. Then not all states allocate electoral votes on a winner takes all method. Two states allocate electors according to the popular vote.

Can the election be a do-over? No, there is no time. The only solution is that the election should be ruled null and void by the Supreme Court and it should be thrown into the House of Representatives. The allegations of fraud are massive. I seriously doubt that 25% of the people voted for Biden because they really thought he was competent. The rest voted for Biden because they hated Trump. The computer has been correct far beyond what even I suspected was possible. Yes, it forecast that this would end in the most violent election since the ’60s. We have Antifa sill protesting and they want to overthrow the United States, capitalism, and colonialism. Besides tearing down whatever they can get their hands on, what is their solution? If the land was stolen from the Indians, then the right thing to do is not tear down statues of Columbus, but get on the next plane and go back to their original country. You can’t have it both ways.

UPDATE: CTH 2.0 Site Challenges on Launch – Apologies to Readers and Users…


Posted originally on The Conservative tree house 2.0 on November 30, 2020 by Sundance

“Glitches” seems like an easy catch-phrase to explain encountered problems in the world of technology; but “glitches” doesn’t reconcile the real human frustration people encounter when they engage with a system that is experiencing a rather unique challenge.

I won’t say we are experiencing a glitch…. CTH 2.0 is experiencing a challenge that has actual emotional consequences…  Here’s the issue in as much non-technical wording as I can muster.

SIDEBAR: For other websites with considerable scale, and considering the deplatforming issue underway, this might also serve as a guide.  Additionally, for site users in any website this might explain some background decision-making on commenting functions that is often left unsaid outside of closed-door meetings.

First, my sincere apologies for the trouble everyone had, and is having, as we launched CTH 2.0 with new host servers.  As you know, our commenting community is our #1 priority and we have years of relationship and trust together.  The challenge before us today is considerable.

When we were told we had to leave WordPress/Automattic platform it was important to us to retain the entire site library that includes over 56,000 published articles and over 7.2 million comments.

Some articles carry up to several hundred citations and the average amount of content within the 7.2 million comment file alone exceeds 40 million lines of metadata.

All of that CTH data took approximately 60 hours to export and transfer (import) to a new site and eventually new host servers. The data was first uploaded to a test site to gauge the scale of data and time.  After that initial transfer timeline was determined the data was then imported to new host servers, CTH and CTH 2.0 were mirrored, and fully migrated away from WordPress/Automattic servers.

The CTH 2.0 site was reviewed, some adjustments made to ensure user friendly systems were carried over, and we were ready to switch the site. That is called a DNS switchover.

As the domain name shifts from WordPress/Automattic to our new platform host the worldwide system of interconnected data networks needs to identify and promulgate searches for “TheConservativeTreehouse.Com” with the new site destination, the new servers.  This process takes place in every country around the world, each with a different refresh rate for DNS activation.

At approximately 7:30pm ET last evening that process was initiated.  CTH search results switched from final destinations at WordPress/Automattic servers to our new server host.

Regionally as each Internet Service Provider (ISP) updated it’s DNS mapping, users were directed to new CTH servers.  CTH 2.0 slowly showed up in every city, state and town as the regions came on-line with updated directories.  The process executed as expected.

We anticipated a significant data pull from initial users that would hit the server network, so we purchased a secondary “cache” service, Cloudfare, to help offset the scale of the data load by hosting the static or older library files.  It’s a weird system but the data starts to promulgate two data-systems simultaneously.  The load on the servers is offset by the ability of CloudFare to host and direct users to older content.

However, in the change to new servers there is no pre-existing room of old “cached” files that don’t need to be responsive to the user.  The entire CTH archive library is essentially being pulled from the Host Servers as the promulgation continues and a new set of cache files is being created that will eventually take some of the load away.

Depending on the library size – for the first 24 hours the new servers are carrying all the load and the data capacity is stressed.  The server host anticipates this heavy load and has a system in place called “autoscale” that activates to allow more server capacity during the DNS switch.

That is one initial load on the servers that improves in time.  Time allows the servers to fully promulgate and get better at working with secondary cache services who take some of the burden.  But in the first hours all of the data load is on the host server.

The secondary issue is where our problem rests.  As each provider gained access to and directed customers to the new servers, many of the inbound users, our community, started commenting.  The scale of our community is significant, we are proud of it.

The CTH 2.0 site content was promulgating new pathways (the DNS changeover) at the same time users started to engage with it.  The cache service was also promulgating. However, the commenting function is a live-time engagement, so the secondary “cache” host doesn’t interact at all with the commenting data-load.

When you write a comment it creates a metadata file. Each comment is a unique url.  Your unique id is part of that metadata, your gravatar or avatar is part of that metadata, the content of your comment (what you write) is part of that metadata and any article links, citations, pictures, gifs, or tweets -each carrying a unique url- is part of that metadata.

The average number of lines of unique metadata in one comment is six to ten lines of code, regardless of the length of your comment.  Your comment creates a mini data-file with its own unique id (the url).  The library of pre-existing comments is 7.2 million.  Multiply that by the lines of metadata and you get well over 40 million lines of code in the pre-existing comment file alone.

♦ Here’s the issue. Whenever you write a unique comment the pre-existing library is searched by a software program to match you to your commenting history.  This avoids duplication (if you hit send/submit more than once), and it also looks for spam or bot signatures.

Because we are using new servers the library of 7.2 million comments (each with 6 to 10 lines of metadata) has to be searched by the same software built into the system to avoid comment duplication.  In essence as you hit submit/send the search goes through the entire library of 40 million lines of metadata looking for your unique id and then responds back to allow the comment to go through.

With only a few people reaching the site it’s not a problem.  However as more and more people are both drawing from the host library of posted content; and simultaneously writing comments that have to go through searching 40 million lines of metadata; the servers get overloaded.

Put 1,000 people on the site at the same time and you get 1,000 x 40,000,000 lines of metadata being searched and queried at the same time.

With one thousand users the servers are trying to: (1) return library results on 11 years of archived posts; and (2) search through 40 billion lines of comment metadata and respond simultaneously.  That’s the data load for 1,000 users.

[On an average day at CTH we hold 25k users/hr simultaneously and a peak avg around 35k to 50 thousand around 9pm ET.]

Last night, typical for CTH, as word spread we had 30,000 simultaneous users return to the website.  Do the math: 30,000 users x 40 million lines of metadata in the comment library search and the servers overloaded…. “504” and “524” notifications were the result on your browser searches.

That’s what happened.

It’s not an excuse for what happened; that’s just what happened.

As the DNS promulgates more fully the servers will be less taxed on the article data retrieval and older files will shift to the cache service.  The weight of the site data will lessen as the cache can step-in, and the servers will be less taxed.  That part is not a problem.

The problem is the sheer scale of the comment library.   Every comment submitted draws a search amid 40 million lines of metadata.   Over time that will also improve, but the comment library is going to take much longer to promulgate; and it doesn’t help that Google search engines are simultaneously crawling through the entire site, including the totality of the comment library, to re-index their search results by pulling data from the new site servers.

One quick solution from the engineering side was to just get rid of every comment older than 90 days so the comment library shrinks to a manageable searchable size.

Another solution to regain the site was to shut down commenting again thereby stopping the search function associated with each unique user posting a comment.

The latter approach would buy time to find another solution that might avoid deleting the comment library.  That is the approach we have chosen right now.  We didn’t really have an option.

When I was asked “why not just drop the old comments” we run into a conversation that is personal for our CTH community.

There’s a few reasons why I wanted the total import of the comment files, one of them I never wanted to discuss…. but to explain to those here today who might also just say get rid of the older comments… I need to share something very important.

Our comment library holds 11 years of prayer request threads.  It was the first function we added to this little hideout.  You may not know it but the admins and I spend a lot of time reading those prayer requests; and yes, we pray for those who write.

Those prayer requests and replies are from real people, our people, our CTH community of people and they are the source of our compass heading.   More importantly, we have lost friends who asked for prayers for themselves and/or their loved ones.  We have held the hands of those people and we have at times had no words other than just to sit still and let them know we are there.

Many of those friends left us and they are in God’s hands now.  Additionally, whether you know it or not the families left behind visit those prayer threads, read the words, and remember the voices of those who are no longer with us.   If we were to delete old comments we would be losing many of those prayer threads, and that would just be too high a price to pay.  It would feel like we were breaking a promise, I cannot do it.

So the tech team has been told deleting comments by date is not an option.  If I need to pay a service to host an archive of those prayer threads, so we can put a link to them, then that’s doable.  But we are not deleting them, period.

The tech guys are looking at other options for how to turn-on comments while at the same time lessening the burden on comment data by reducing the library.   There has to be a way to do it and that’s the challenge.

I apologize unreservedly for this issue.

I apologize that you cannot comment right now.

This issue within the launch of CTH 2.0 is entirely on me.

The tech people who worked on this massive export and import of data have done outstanding work.  I am the person who wouldn’t budge on retention and transfer of the entire CTH data library to include every comment by this community.  This 11-year labor of love will not be taken apart.

There’s a solution out there and we are sharp enough to figure it out.

Warmest love and deepest appreciation for your understanding,

~ Sundance…

Share this:

UPDATE: “Liberty One Has Landed” – DNS Server Switch Activated – Welcome to CTH 2.0


Posted originally on The Conservative Tree House 2.0 on November 29, 2020 by Sundance

Liberty One to Ground Control: “New site reassembly complete” … “Activate DNS server switch” … “Transmitting new CTH 2.0 beacon” …  “Message in 3… 2… 1″….

…. “Welcome Back Everyone, We Sure Missed You Guys!

Hello everyone, we made it.  Hopefully it looks awfully familiar around here. Pull up a comfy rock, sit back around the campfire…. Lets have a talk, because it’s time to get back to business.

Clear your computer “cache and cookies”, search or use your bookmarks for CTH again, and your browser should redirect you to the correct website on brand new servers.

Hi !  Please Check-in…

A total of 69 chronologically distributed files containing massive terabytes of CTH library data (increasing exponentially by date) have been transferred.  The library is intact.

Trillions of ‘ones and naughts’ traveled through digital space in electromagnetic time and then landed thousands of miles from their point of origin…. reassembling by falling into the exact and precise sequence needed to re-emerge.  Quite remarkable.

The only thing lost was the comments during switchover from November 27 (11pm ET) to now.  All other content transferred seamlessly thanks to the incredible people who ran point on the tech transfer for the past week.   We are so very thankful.

Love to all, and a big wide smile….  Hello again.

UPDATE: Mission CTH Liberty Underway…


Posted originally on The Conservative Tree House on November 28, 2020 by sundance

Ground Control to Liberty One: ..”We have main engine separation, next stop – Freedom”…

As the CTH community is aware, WordPress/Automattic has demanded our voice leave their platform. Effective this moment, “Operation CTH Liberty” is underway, and we are separating from main host web servers. {Go Deep} During this transitional phase we are in, we will have a controlled comment blackout until the site migration is complete to new host servers. You may or may not be able to comment. The anticipated transit time is 30 hours to new host.

By taking this painstaking approach, we are ensuring that all internal links do not result in a “404” dead link notification. Meaning the library will remain intact, and all external links that lead to the CTH library will be able to find them. Additionally, and/all citations within the CTH library will be retained, and people will be able to use all the embed links; and also importantly, all prior links to your previous comments are retained.

During the transition and data transfer, we will need to shut down commenting function for CTH (WordPress) until CTH 2.0 launches. The mirroring of the site during this process will take (based on the test run) approximately 30 hours +/-. As a result, it is highly likely comments will be closed for around two days. Unfortunately, there is no other way to pull this off; it is simply a matter of volume and scale.

We will continue to post new articles and you will be able to see them, you just might not be able to comment on them until the full data transfer to Treehouse 2.0 is complete.

[Remember, the articles from CTH/CTH 2.0 cross-post onto Twitter, and you can also comment there. Or use the Twitter link to return to the CTH 2.0 article when live]

♦ The domain name will remain the same: “TheConservativeTreehouse.com”, and should be seamless in transition to the new website.  However, after CTH 2.0 launch you may need to clear your browser “cookies” and “cache” so that your search or bookmark reaches the new servers accurately.

How you can tell – If you find yourself only finding older articles when you visit CTH Sunday(ish) this will be the problem.  Clear your “cache and cookies”, search or use your bookmarks for CTH again, and your browser should redirect you to the correct website.

When the comments go live again, please be patient if you get hung up in a moderation cue. One of our challenges will be the absence of Askimet spam filtering. It may take time to release some comments if they are hung up in moderation. The site admins do a great job with comment moderation and release so it shouldn’t be too much of an issue; and quite frankly, there are likely to be benefits from not having the WordPress software filtering through the comments as they post. Spam removal will be a priority.

Please bear with us as we work through some of the challenges of comment moderation in our new platform. It should be seamless, but just in case… well, patience is appreciated. Be assured we will work diligently during this go-live phase to deal with any comment issues as rapidly as possible.

Over the Thanksgiving holiday, WordPress/Automattic disabled CTH’s ability to filter, review or disable vulgar content on our site. Given the unwarranted, pre-textual de-platforming of CTH by the pro-censorship board of Automattic, CTH cannot ignore that such manipulation is to maliciously interfere and damage the reputation of CTH.

Because of Automattic’s purposeful actions, we have been forced to monitor every site comment in real time for appropriate content over the past 48 hours and remove content that seems purposefully targeted to tarnish our reputation and public image. CTH expects to be Back to normal functionality in 30 hours. Thanks for bearing with us, and thank you for your first hand witness of the tactics of deplatforming and censorship in America.

We are chomping-at-the-bit to get back in this fight for our nation; and do not think for one moment we are not aware our specific targeting was purposefully timed to disrupt our research ability.  We know exactly what Big Tech and the left-wing political operatives executed.  They know that we know; and when we know – YOU KNOW.

Myself and the incredibly hardworking site admins consider ourselves stewards to this community.  YOU are what matters, so another important part of Treehouse 2.0 is to ensure your ability to analyze, discuss and provide your comments on the subject matter.  We will NEVER remove a commenting function from our website.  In fact, it is the crowd-sourcing work we have done as a community that has been the most thrilling and brilliant part of our work together. I will never lose that focus.

The key to Treehouse 2.0 is recognizing we are building something within a system that wants to see us removed. Being proactive about that will hopefully make us better stewards for our conversation. Remember, YOU are the important part.

Without you CTH doesn’t really have a purpose. I could stand outside shouting at trees with no impact; but together, sitting on the figurative porch, the conversation is rich with unique skill-sets, subject matter experts and life-long experiences that make discussion so much more valuable. Myself and the CTH admin team cherish the value you represent.

Over the next roughly 30 hours we will transfer the data from a decade of research into our new home.  We will transfer massive bytes of data across the space between our old home and our new servers, but the key ingredient will always be missing until we are united with our commenting community.  We are a little sad, yet nervous and exited to take this step; and there’s no community we would rather share this journey with, than you.

Thank you for your support and fellowship.  We will always work diligently to deserve it.

The rebel alliance will reassemble with comments as soon as possible.   We shall meet at the Old Mill and ride again…

Love to all,

~ Sundance