Yesterday President Trump signed a social media executive order that specifically mentioned Twitter. Twitter doesn’t seem too concerned or scared though and nor should they be as many legal experts have weighed in and stated that this EO doesn’t hold much weight. The executive order goes after CDA Section 230. This is bad. It’s something we wrote our concerns about here.
This morning Twitter once again editorialized one of the President’s tweets, but this time they took it a step further. They covered up his entire tweet with their editorial comment and made it so the President’s tweet could not be commented on or liked by anyone on the site.
The solution is for the President to join and openly support alternative technology platforms like Gab and others.
If he leads the world off of Silicon Valley platforms: tens of millions of people will follow.
If not, Twitter and Silicon Valley will continue to crush any and all dissent.
Including from the President of the United States of America.
We have the President’s Gab account ready and waiting.
As you know we deployed a new update to the Gab Social interface this past week. This new update resulted in a huge uptick in traffic, which resulted in our existing servers being stretched to capacity very quickly.
Thankfully we have new and improved server hardware that we are in the process of upgrading to as we speak. We will be posting progress updates to the Gab Status page on here on a daily basis.
We are currently moving terabytes of data and this transition is not an easy one. There will be rolling downtime and performance issues for the remainder of the week. We will be crediting all GabPRO members with double the amount of downtime once things are back up and running. Thank you so much for your patience and understanding.
The Gab Team
May 23rd, 12:30pm EST
The site is back up and running. We are working on an outstanding issue with image uploading which should be resolved tonight.
May 22nd, 12pm EST
We made dramatic improvements to several database queries and have begun production testing to gather information on their performance. We will be continuing this process throughout the day, Gab will still have rolling downtime during this testing.
May 21st, 4:15pm EST
Notifications are now loading chronologically as expected and performance has improved dramatically. We are on track for being up by end of week, but are doing everything we can to get you the best Gab experience we can as soon as possible.
- Replicating Gab’s terabytes of data to a 2nd database server (will take time)
- Performing system-level maintenance and configuration of existing production servers
- Testing and qualifying back-end performance enhancements
- Continuing to optimize the home timeline service for everyone
May 20th, 5:30pm EST
The data optimization discovered earlier is being applied to the production database. The change will then be tested on current production servers. We will be measuring for expected performance improvements. The team continues to make additional optimizations throughout the system while the data situation is being corrected. Work continues on the front-end to address issues with Notifications and enhance their performance.
May 20th, 2:30pm EST
The team has identified a major data optimization in Groups and is resolving it now. This change reduces an area of data use by an order of magnitude without changing how Groups work.
May 20th, 9am EST
-Working in our datacenter to configure new hardware
-Continuing to clean up existing backend code
-Working on further optimization of the new frontend code
May 19th 9pm EST
-Optimizing queries on the new Gab design
-Cleaning up existing backend code