Even before adopting net neutrality, here are 26 actions by which the Obama administration has already proven itself to be incompetent when it comes to the internet
The fact that Obama refuses to allow the public to see his 332 page net neutrality plan until after its implementation is voted on is, by itself, reason enough for me to oppose the plan.
I would think that even the biggest supporters of net neutrality would be curious as to why Obama won’t let people see his plan until after it is implemented.
However, in addition to that, here are 26 examples of actions by the Obama administration which prove that it is incompetent when it comes to the internet.
Any one of these examples, by itself, is proof that the Obama administration is incompetent when it comes to the internet.
Taken together, these 26 examples make me wonder why anyone, even the most liberal of liberals, would trust the Obama administration to regulate the internet.
1) Obama knew about the defective Obamacare website a month before it went online, but he still allowed it to go online anyway.
2) Before Obama hired Kathleen Sebelius to run the defective Obamacare website, she had had a long track record of failure at running websites when she was governor of Kansas. But Obama hired her anyway.
Kansas state representative Scott Schwab said of this:
“We pretty much expected HealthCare.gov to fail, because she has a pattern of failing on these big initiatives.”
3) Federal employees who had tested the defective Obamacare website before October 1, 2013, gave it their approval.
4) Obama said he was “mad” over the defective Obamacare website, but refused to actually fire anyone over it.
6) When the defective Obamacare website went online on October 1, 2013, it had already cost $634 million.
However, David Kennedy, president of the technology firm TrustedSec, said that even if the Obamacare website had worked properly, it should not have cost more than $10 million. Luke Chung, president and founder of the technology firm FMS, said he agreed with Mr. Kennedy.
7) Instead of hiring competent programmers to create the Obamacare website, Obama hired CGI Federal, a company that was run by Toni Townes-Whitley, who attended Princeton University with Michelle Obama.
8) In December 2013, Michelle Snyder, the Obama official who oversaw the building of the defective Obamacare website, announced her retirement. Obama did not fire her. By retiring, she will be allowed to collect her full pension and benefits.
10) The Obamacare website couldn’t handle as much traffic as a website which is run by one guy in his pajamas from his apartment.
drudgereport.com is run by Matt Drudge, who runs the website in his pajamas from his apartment. I’ve visited his website just about every day since the late 20th century. It runs very well. His website has gotten as many as 45 million hits per day.
On the first day of the Obamacare website, it had 5 million visitors. It could not handle that amount of traffic.
11) The Obamacare website “looks like nobody tested it.”
President Obama signed Obamacare in March 2010. He had three and a half years to create and test the Obamacare website.
However, in October 2013, CBS News quoted Luke Chung, an online database programmer who supports Obamacare, as saying the following about the Obamacare website:
“It wasn’t designed well, it wasn’t implemented well, and it looks like nobody tested it… It’s not even close. It’s not even ready for beta testing for my book. I would be ashamed and embarrassed if my organization delivered something like that.”
12) When the New York Times asked the Obama administration to identify the private contractors who had screwed up the Obamacare website, the Obama administration refused to answer.
13) The Obamacare website launched a “denial of service attack” against itself.
IT experts who had analyzed the data going to and from the Obamacare website said the reason that people could not use it was because it was launching the equivalent of a “denial of service attack” against itself. They said the website was sending and receiving massive amounts of unnecessary data back and forth between itself and users’ computers. The IT experts attributed this to bad programming, and said that adding more servers would not fix the problem.
14) During more than 40 attempts to log in to the Obamacare website over a period of 11 days beginning on October 1, 2013, a New York Times reported was never able to log in.
15) Even after the Obamacare website failed, Obama still refused to fire Secretary of Health and Human Services Kathleen Sebelius.
16) There is “no reasonable expectation of privacy” at the Obamacare website.
The source code for the Obamacare website states:
“You have no reasonable expectation of privacy regarding any communication or data transiting or stored on this information system. At any time, and for any lawful Government purpose, the government may monitor, intercept, and search and seize any communication or data transiting or stored on this information system. Any communication or data transiting or stored on this information system may be disclosed or used for any lawful Government purpose.”
17) Legitimate shopping websites such as amazon.com allow users to browse merchandise without having to enter their personal information. However, the Obamacare website requires users to enter their name, social security number, and other personal information before they are allowed to look at the insurance plans.
18) During the first two weeks of October 2013, a reporter from CNN repeatedly tried to log in to the Obamacare website, and was never able to log in.
19) The Obamacare website was built using 10-year-old technology.
20) The Obamacare website had between 10 and 20 times as many lines of code as it should have had.
The Obamacare website has 500 million lines of code.
Dave Kennedy, the CEO of information-security company Trusted Sec, said that a website for a project on the scale of Obamacare should actually have between 25 million and 50 million lines of code.
21) A New York Times writer gave Obama a grade of ‘F’ for the rollout of the Obamacare website.
On October 25, 2013, New York Times writer Uwe E. Reinhardt wrote:
“… who exactly should be assigned the F for the troubled rollout of HealthCare.gov?”
“Once elected, a president becomes chief executive of a giant federal enterprise. Anyone familiar with corporate management would have thought that for as ambitious and technically a complex project as the initial rollout of HealthCare.gov – so important to many uninsured Americans and so politically important to the White House – the chief executive would have remained in very close touch with the management team overseeing the project and thus would have been briefed daily or at least weekly on the progress of the project and especially on any problems with it.”
“… the blame for the disastrous rollout of HealthCare.gov goes to its entire management team, to be sure, but primarily to the chief executive on top of that project. In my view, not only the proverbial buck stops on the chief executive’s desk, but, for the management of this particular project, the grade of F goes there as well.”
22) “4 Things The US Government Accomplished In Less Time Than A Working Obamacare Website”
In November 2013, camharris.us reported:
4 Things The US Government Accomplished In Less Time Than A Working Obamacare Website
From the day that the Patient Protection and Affordable Care Act went into effect to the morning that the federal healthcare exchange went live, 1288 days passed. 3 years, 6 months, and 8 days. In all that time, our federal government could not construct a website that actually worked, and we are still waiting for a final product.
Here are 4 things the United States government accomplished in less time than it has taken to build a working website:
1. We Fought World War I
April 6, 1917-November 11, 1918
1 years, 7 months, 6 days
2. We Fought A Bigger War
December 7, 1941-May 8, 1945
3 years, 5 months, 2 days
3. We Built The Bomb
June 17, 1942-July 16,1945
3 years, 1 month
4. We Orbited A Man Around The Earth
October 7, 1958-February 20, 1962
3 years, 4 months, 13 days
23) In December 2013, it was reported that the Obamacare website was in violation of federal security laws.
24) The Obamacare website had such horrible security that it was hacked by one person in less than four minutes with nothing but a regular web browser.
In January 2014, hacking expert David Kennedy was able to hack into the Obamacare website in less than four minutes, using nothing but a regular web browser. During that time, he was able to access the private information of 70,000 people.
25) The Obamacare website is exempt from laws that require other websites to tell their customers when their private information has been breached.
26) Four days before the defective Obamacare website went online, the White House gave itself a waiver which allowed the website to go online, despite the fact that it was deemed to be a high security risk.