This is relevant to pizzagate for this reason: TPTB have been trying to frame Trump for ties to Russia because they KNOW that Trump is not controlled or compromised to prevent him from investigating #pizzagate/#pedogate.
I came across this recently deleted thread: https://voat.co/v/pizzagate/1711328 and believe that this is a major lead for us to pursue as it is absolute proof that the Emily McMullin connection has been manipulated and is being actively covered up by both WHOIS (which now shows https://www.whois.com/whois/trump-email.com)) and Archive.org (explained below), which both look compromised. So far, archive.is (from a 3/7/17 snap) is the only place showing the history of Emily McMullin updating the registration of trump-email.com on 6/29/16: http://archive.is/tAIO8
Here is one of several articles that originally exposed this attempt to frame Trump as connected to Russia via a server set up to connect to two Russian banks: http://www.northcrane.com/2017/03/06/breaking-mcmullin-setup-trumprussia-server-that-allowed-fisa-wiretap-warrants/. Trump-email.com was specifically manipulated to create a server connection to 2 Russian banks. This was done on 6/29/16 by Emily McMullin, tied into the efforts by Obama/Lynch to get FISA approval to spy on Trump. The ICANN WHOIS, which I have seen personally a few days ago, was changed to remove her name and replace with [email protected], but the update date still shows as 6/29/16, meaning that this is a cover up occurring at the ICANN WHOIS directory level - the central registrar and repository of record - which is HUGE.
Archives have been manipulated as they do not show what showed before but what shows today. 1/11/17 archive.org shows the same info as showing currently, despite the registrar being edited on 3/8/17: http://web.archive.org/web/20170111070008/https://whois.icann.org/en/lookup?name=Trump-Email.com
I just tried to archive this article on archive.org (http://www.northcrane.com/2017/03/06/breaking-mcmullin-setup-trumprussia-server-that-allowed-fisa-wiretap-warrants/)))), and IT WILL NOT LET ME DO IT. Archive.org is clearly compromised.
Archive.is has a 3/6/11 archive of article: http://archive.is/x4JWb
Edit: Error in title: The address is trump-email.com (not org). Apologies!
Edit 2: These bullets show the differences in results in the registrar:
It is really interesting that bullet 1 and bullet 2 are not a perfect match. They should be pulling from the same database. It is proof that the first bullet, the archive from the ICANN WHOIS database, was hard-code edited to eliminate the trail tying things to Emily McMullin (not pulling from the same database). I tried to archive each bullet on archive.is:
view the rest of the comments →
throwaway89209834 ago
Your connection between this and pizzagate is pretty weak. I would say that it is valid because it involves websites that we use and rely on in our investigations.
Anyway...
So was sli.mg and, even though its in iceland, archive.is is still vulnerable. This is what happens when the corrupt own the institutions that have access to all of this centralized infrastructure or people who know how to break into it.
I kinda stopped trying to collect data after realizing I don't have a good way to ensure it can remain online, secure and not turn into an information silo. I have been playing with IPFS (interplanetary file system) in my lab, which allows a decentralized web meaning that, to take down a website, or any content hosted on the ipfs server, they would have to take down everyone who chose to replicate (pin) the data. It works pretty much the same way as a torrent and all content is hashed using merkleDAG's the same as a cryptocurrency blockchain to ensure that data cannot be manipulated. It essentially allows for a decentralized 'permanent' web.
The neat thing is that there is already an existing project that combines the IA's wayback system on top of IPFS.
https://github.com/oduwsdl/ipwb
Also there is a project for hosting a wiki on top of IPFS.
https://github.com/jamescarlyle/ipfs-wiki
And a project for hosting a pastebin/img dump
https://github.com/rameshvarun/ipfs-share
This means that if enough people would volunteer to host the contents, we could potentially have a way to store information that is much more resistant to manipulation and take down.
The only reason I am not totally on-board with this and going nutty over how cool it is, is because 1.) It is a new protocol, there are sure to be some bugs (same with any software ) and 2.) By design the protocol shares both the users public and private IP. It has to be carefully routed to ensure your IP is not leaked and even then a bug in IPFS or the VPN could cause a leak.
So at this time, it should only be run by more advanced users who are comfortable running something potentially vulnerable on their system (IE they know how to set up a sandbox, monitoring, and lock down potentially dangerous processes) and preferably have a system just for that task and no other personal data is hosted there. Hopefully I will have an example and tutorial for folks in a few weeks if I get the time.
The great thing is that malicious actors can replicate the data but will not be able to manipulate it thanks to the way to stores file cryptographically and uses merkleDAG to verify its contents.
What would be really cool is if I could put together a buy list for parts to put together a raspberry pi and 1TB HDD for storage and anyone who wanted to be involved in replicating the data could buy those, run a setup script, put it on their network and be come another node in the ipfs network.
Something to think about for now, I'll be making a post about it soon.
reasonedandinformed ago
Thank you for your deep thoughts in the post. I see two levels of relevance:
They are trying to take down Trump because they fear he will go after PG.
We have hard evidence of manipulation at the level of ICANN and archive.org. This is important to document as we know we have run into this before with PG, in addition to the LSM and social media manipulation and censorship.