I just got this. Yikes.

Not for me. I get a weird error now.

It's coming out. Be prepared everyone... This is what "fake news" was all about

Please elaborate on your thoughts.

I think WL has been compromised since before the election. FBI/CIA has taken over WL social media accounts and now we are seeing them take over the WL domain (messing with the certs). I believe the switch has finally been activated and we will see the files trying to leak onto the web. As long as WL doesn't send an official leak notice any fresh files hitting the web will be deflected as "fake news".. Things are speeding up behind the scenes... Buckle up!

That's not good..

I've been getting that error on chrome all day long today

I am still getting the first page, and many of the links. I only get the error when I click the Wikileaks header/logo.

I'm getting everywhere as well, even uscourts.gov

Got the same error.

seems normal

Their twitter account hasn't been 'normal' since mid-October when Assange's connection went dark. He was obviously taken, given the pre-commits and now their security certificate has expired and can no longer be faked.

He couldn't manage all of it alone. He had support employees, but when they raided the embassy and cut off his Internet, they likely had a coordinated attack in multiple locations, compromising whoever was managing the Twitter account too. The Podesta emails were on an automated algorithm release schedule.

See the series of Tweet typos that spell out help him. The person sending those messages was obviously under duress, and they were later deleted. Another person about a month later posted to 4chan/pol/ saying MI6/CIA had Assange, and that he [anon poster] had one last tactic that he was going to try, but it required travel. That might have been another deadman's switch of sorts.

Agencies like CIA and Interpol were obviously coordinating to take down the Internet across Europe and eastern US, remember when the Internet kicked out for a day or so back in November? That was likely to trial and error to figure out where the Wikileaks mirror sites were, and to possibly interupt Assange's deadman's switches. Assange is so talented he probably wrote his own deadman's switch programs. (I say is in the hopes that he's still alive and well somewhere.)

Glad to see the information I research is helping others!

You can get some more insight from Assange in his interview on C-Span (of all sources) promoting the book, The Wikileaks Files.

Not only were they automated releases, their stochastic algorithm scanned publicly available information like social media posts, (they already knew about all the insights before publishing by the way) and was automatically grouping release email ranges, then publishing those automatically in the batches we saw. This is how Assange was able to go on interviews and claim Hillary was going to go down, even though they still thought she'd get elected.

The easy answer is yes. The more complex answer is yes, haha. It would be up to his supporters to download the insurance files while Wikileaks were NOT compromised before Oct 19. The pre-commits as far as I understand were hashes. They are used to ensure the validity and integrity of any specified files. Whoever or whatever is being addressed (in that case, John Kerry for example.) would be some sort of file group, or possibly a zip file within a tar file that the supporter has already downloaded.

Secret keys might be released in any number of ways. I haven't needed to use them before but there are marketed deadman's switch web app services, and it seems they are set up to email directly to a few contacts. You might imagine, that if your file has already been downloaded by thousands of people, and you no longer can login anywhere, it will trigger, and you would WANT those in possession of your files to get your passphrase and unecrypt those files. Ideally, they then continue this process, so that truth can live on. Your login/do not trigger intervals could be custom specified, one week, a month, one quarter, one year. So it might be Oct 2017 before we see another really big information release from DKIM verified wikileaks files.

Before Wikileaks broke down, we probably only saw less than 10% of the content they actually knew about and possessed. They were trying to stay relevant by releasing in batches, as far as I understood their strategy to be.

I'm on just about every few hours. So pretty recent. A few hours recent..

Some people are saying their twitter seems abnormal from usual posts. I don't Twitter, but I have been hearing people say this all week. I don't know what has changed or how though.

also this

None of the verification codes have matched since Assange went missing. They're definitely compromised and Assange is most likely dead. Someone needs to start a new wiki leaks

And now this

It does not look good. But much surrounding Wikileaks is not looking too good these days.

All good here.

Likely your traffic is being intercepted.

He couldn't manage all of it alone. He had support employees, but when they raided the embassy and cut off his Internet, they likely had a coordinated attack in multiple locations, compromising whoever was managing the Twitter account too. The Podesta emails were on an automated algorithm release schedule.

See the series of Tweet typos that spell out help him. The person sending those messages was obviously under duress, and they were later deleted. Another person about a month later posted to 4chan/pol/ saying MI6/CIA had Assange, and that he [anon poster] had one last tactic that he was going to try, but it required travel. That might have been another deadman's switch of sorts.

Agencies like CIA and Interpol were obviously coordinating to take down the Internet across Europe and eastern US, remember when the Internet kicked out for a day or so back in November? That was likely to trial and error to figure out where the Wikileaks mirror sites were, and to possibly interupt Assange's deadman's switches. Assange is so talented he probably wrote his own deadman's switch programs. (I say is in the hopes that he's still alive and well somewhere.)

Not for me. I get a weird error now.