Republished from Doomstead Diner
January 27, 2013 | By Peter
The world recently suffered a great loss, when it lost Aaron Swartz to suicide?
Aaron was like a beacon of shinning light in a mostly gray and foreboding world. He was highly intelligent and principled. He made all of our lives brighter. He was in the forefront of the fight to keep the internet a place of openness and honesty rather than let it become a closed tool only beneficial to powerful interests such as the mass media now is.
Aaron was directly responsible for helping create the RSS newsfeed standard that caused document 1, referred to in the investigation, linked to at the top of this article, to be discovered.
We do not know for sure who first discovered the existence of this document. However it happened, the discovery was a massive win for internet openness and freedom. Whoever that person was would need to have a deep understanding of how and where information is stored on the internet. Also of how information is indexed for easy retrieval.
Aaron was that type of individual. He also had the intent to serve Truth and Justice, particularly on the Internet.
If I had to pick just one person capable of making such a discovery I would pick Aaron.
The events at Sandy Hook likely attracted his attention. He would then start researching on the internet to find the truth, using the needed tools, which he was intimately familiar with.
RSS feeds, the standards of which he helped put in place, allow search engines to report news items created on the internet, about important events, almost instantly. Being an expert on how RSS feeds function, and where the records that such feeds create are stored, he then likely started to search through those records to see what he could find.
Aaron likely discovered the RSS feed record the Arlington Schools Website sent out that announced, rightly or wrongly, that the horrendous events at Sandy Hook School occurred on December 10th, 2012, 4 days before they actually happened on December 14th 2012. Discovering the RSS record would have allowed Aaron to find the Google cache record displayed as evidence in our investigation, with only one click.
In the normal course of events it is highly unlikely anyone would ever have found that cache record. Only the RSS record would publicly show it existed. To initially find the record directly in the cache would require someone knowing the document’s exact URL and name. If no one knew of the documents existence, they could not know what to look for.
Whoever the person was that first found the document in Google’s cache, we all owe them a huge debt of gratitude. I strongly suspect Aaron was actually the one to discover that record at Google. He likely paid for that discovery with his life.
With that highly likely possibility in mind I would like to dedicate this Investigation to Aaron. Whether or not he was the one who first found this record, his efforts in developing RSS feeds were instrumental in their being discovered.
We all owe it to Aaron to make sure that his efforts to make the world a better place were not in vain. We must continue the struggle he was engaged in, and attempt to build upon his efforts, until the world is a place of justice and honor such as he attempted to create.
This investigation would not be taking place without principled people like Aaron struggling to protect everyone’s rights.
Aaron, Thank you.
For the back story about the Arlington Schools website, see:
I am going to explain to you in this article how those document came to appear on the internet on the Published Dates shown, December 10, 2012 and December 13, 2012. I will also explain how the search return came into being. In order to do this I am going to ask you to suspend disbelief so you can follow the timeline explaining the documents.
Events like 9/11 have demonstrated that news items about them appear almost instantly after such events. Many are complex documents that would be impossible to create in that short a period of time. If someone is preparing a false flag the most effective period to introduce your desired interpretation of the event is immediately after the event while people are still in shock. In order to meet a tight deadline there are many trusted people working in the background preparing documents and then sitting and waiting to pull the trigger and make them public the moment the event is planned to occur. These people are scattered all over and working off their own script with a time to make their information public. CMI (Crisis Management Inc) which had author permissions on The Arlington School Website as a contractor to upload their material to the website as needed. They could upload, create links to their material, and publish news announcements all from their own offices without anyone from the School being involved. The School shootings that took place in Sandy Hook on December 14, 2012, were originally planned to happen on December 10, 2012.
If you check on a calendar you will see Dec 10 was a Monday and a school day so the event could have been planned for that date.
DECEMBER 10, 2012
Everyone involved with media material had the material prepared referring to the date Dec 10, 2012.
On December 10, 2012 someone at CMI was waiting to pull the trigger and publish the news item (Document 1) and related documents such as the pdf the news item announces.
For some reason the event was called off at the last moment.
Everyone who had planned to submit material was frantically called to NOT submit their material.
The message for some reason didn’t get through to CMI in time and they submitted the pdf, created the link to it, and published the news item shown in Document 1 .
The other anomalous documents predating Dec 14, 2012 that appeared all over the Internet originated the same way. (See “Sandy Hook RIP/donation webpages created BEFORE the massacre,” Jan. 8, 2013; and “Another Sandy Hook fundraiser that pre-dates the massacre,” Jan. 17, 2013. ~Eowyn)
Because of a technicality (RSS Feed) that is explained by the developer of the program that manages the Arlington Schools site a record of the document immediately left the site and was submitted to people hooked up to the feed as well as to Google which published the item for availability in their search engine. (see document 3)
Google took the opportunity while going to the site to capture the thumbnail of the page seen on the right of document 2 to also put it into their cache database.
In the Technical Discuss Thread at http://fellowshipofminds.wordpress.com/2013/01/21/sandy-hook-phony-documents-open-thread/#comment-164225
Jeremy the developer of the software SpireCMS which the School uses to manage their website stated: “When a news item is created in our system, it is pushed out via an RSS feed and, Google has it indexed usually under 24 hours.” The above means the article could be found on the Google search engine on that date and also in their cache shown in Document 1.
The search record was scrubbed by Google for this Dec 10, 2012 item, but events that took place on Dec 13, 2012 caused an identical entry to be made only with a published date of December 13th. I’m not sure why it wasn’t scrubbed by Google before today. It is shown in Document 3.
DECEMBER 13, 2012
The Sandy Hook Shooting event was rescheduled to this date and was again scrubbed. It Was a Thursday, also a viable date.
It was again scrubbed for some reason.
CMI again did not get the word to not publish in time.
They published the news item again, on Dec. 13, but this time with a published date of Dec 13, 2012 causing another RSS submission creating Document 3 and also a second cache record (Document 2).
Jeremy stated above that “Google has it indexed usually under 24 hours” which means Document 1 would originally have shown either “as it appeared on 10 Dec 2012 or possibly 11 Dec 2012.”
The December 13, 2012 (Document 2) would originally have shown either “as it appeared on 13 Dec 2012 or possibly 14 Dec 2012.”
No one in the loop realized there was an RSS feed on the news items at Arlington School and that the 2 pages (Documents 1 & 2) were recorded in the google cache.
AFTER DECEMBER 14
Some bright Internet users discovered the cache records predating the actual events and all hell broke loose.
The people behind the false flag frantically tried to cover up these incriminating cache records and the search return.
For technical reasons too complex to explain here, it was impossible to erase the records.
Publicly removing the cache document after they were found would also be suspicious.
As a temporary fix someone authorized by Google edited the records as below.
Document 1, which first read “as it appeared on 10 Dec 2012 or possibly 11 Dec 2012 was changed to read 18 Dec 2012” — a date after the events of December 14th. This document was still suspicious but at least is showed it was recorded after the event it announced.
Document 2, which first read “as it appeared on 13 Dec 2012 was changed to read “as it appeared on 12 Jan 2013” — a date after the events of December 14th. This document was still suspicious but at least is showed it was recorded after the event it announced.
To make these changes at Google would take no more than about two minutes. All that needed to be done is to select the records in the database and edit the field that holds the date Google recorded the record.
JANUARY 25, 2013
Google decided that the evidence implicating them in these events were getting too dangerous to leave available and removed them from public view even though that looks very suspicious.
This happened because I stated publicly that it is impossible for a document — published with an RSS feed request to Google — to take 30 days as shown in Document 2 and 8 days as shown in Document 1 after the developer publicly stated at http://fellowshipofminds.wordpress.com/2013/01/21/sandy-hook-phony-documents-open-thread/#comment-164225 : “When a news item is created in our system, it is pushed out via an RSS feed and, Google has it indexed usually under 24 hours.”
There is an enormous amount of corroborating evidence that I described before at Fellowship of the Minds.
If you find the information above compelling enough to look further, and if I survive to tell about it, this discussion will be continued.
That Google is currently scrubbing the evidence does not bode well for those publicly explaining it. Although Google can hide the incriminating evidence from the public, they cannot remove the internal traces from their servers. We who made screencaptures and didn’t clear our browser histories have evidence they existed to the last date we accessed it. Guard that information well.
I am going to stop here to let you consider what I said.
Peter continues to make his case that the CMI was uploaded online BEFORE the massacre, as a prosecutor would in a criminal trial. Please go to our technical discussion thread about this post, “Sandy Hook Massacre: The People v. Crisis Management Institute,” by clicking here.