Source of timeline: https://www.documentcloud.org/documents/3259984-Trump-Intelligence-Allegations.html … Source that RU had had success hitting major NATO targets: http://www.thedailybeast.com/exclusive-russian-hackers-target-the-pentagon … https://labsblog.f-secure.com/2015/09/17/the-dukes-7-years-of-russian-cyber-espionage/ … First 2 are links in the post -- you might try that? You should definitely check out the first one. It'll rattle your brain.
No. As a little exercise in critical thinking let's see if you can find it yourself. Go ahead! I've told you the outlet, subject, date. Hint: Use Crowdstrike too.
-
-
All this tweet shows is that you don’t know what “critical thinking” means.
-
Two things you should learn: 1. Correlation is not causation 2. When you resort to ad hominem in a debate, you automatically lose
-
So you couldn't get the Google to work?
-
I’m on a plane flying over the Midwest. The WiFi isn’t the best, but yes, I found it. This is specifically about the DNC hack and not about greater efforts to undermine the general election through, for example social media. This correlation does not substatiste your claim.
-
Remember how we've already established that there was a really good NYT article, more accurate than anything in dossier, in June 2015, which is a year before June 2016, in case you find that math hard?
-
You're contesting that June 2015 is before June 2016? I've decided you must be a Russian bot bc no human could be this stupid.
-
You’re trying to argue that because there was a NYT piece from 2015 about hacking, that’s the same as widespread reporting/public knowledge of Russian interference in the election. This is obviously ridiculous. When were you first aware of the NYT piece?
- 14 more replies
New conversation -
-
-
Oh, and that you can’t corroborate your bullshit. But that’s been obvious the whole time. The irony is that you’re trying to debunk something, but you have no credible citations that support the claims you’re making.
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.