Showing posts with label Wikileaks. Show all posts
Showing posts with label Wikileaks. Show all posts

Saturday, November 30, 2013

The Spy Files

The Spy Files

 | Dec 1st 2011

WikiLeaks: The Spy Files

Mass interception of entire populations is not only a reality, it is a secret new industry spanning 25 countries

It sounds like something out of Hollywood, but as of today, mass interception systems, built by Western intelligence contractors, including for ’political opponents’ are a reality. Today WikiLeaks began releasing a database of hundreds of documents from as many as 160 intelligence contractors in the mass surveillance industry. Working with Bugged Planet and Privacy International, as well as media organizations form six countries – ARD in Germany, The Bureau of Investigative Journalism in the UK, The Hindu in India, L’Espresso in Italy, OWNI in France and the Washington Post in the U.S. Wikileaks is shining a light on this secret industry that has boomed since September 11, 2001 and is worth billions of dollars per year. WikiLeaks has released 287 documents today, but the Spy Files project is ongoing and further information will be released this week and into next year.

International surveillance companies are based in the more technologically sophisticated countries, and they sell their technology on to every country of the world. This industry is, in practice, unregulated. Intelligence agencies, military forces and police authorities are able to silently, and on mass, and secretly intercept calls and take over computers without the help or knowledge of the telecommunication providers. Users’ physical location can be tracked if they are carrying a mobile phone, even if it is only on stand by.

But the WikiLeaks Spy Files are more than just about ’good Western countries’ exporting to ’bad developing world countries’. Western companies are also selling a vast range of mass surveillance equipment to Western intelligence agencies. In traditional spy stories, intelligence agencies like MI5 bug the phone of one or two people of interest. In the last ten years systems for indiscriminate, mass surveillance have become the norm. Intelligence companies such as VASTech secretly sell equipment to permanently record the phone calls of entire nations. Others record the location of every mobile phone in a city, down to 50 meters. Systems to infect every Facebook user, or smart-phone owner of an entire population group are on the intelligence market.

Selling Surveillance to Dictators

When citizens overthrew the dictatorships in Egypt and Libya this year, they uncovered listening rooms where devices from Gamma corporation of the UK, Amesys of France, VASTech of South Africa and ZTE Corp of China monitored their every move online and on the phone.

Surveillance companies like SS8 in the U.S., Hacking Team in Italy and Vupen in France manufacture viruses (Trojans) that hijack individual computers and phones (including iPhones, Blackberries and Androids), take over the device, record its every use, movement, and even the sights and sounds of the room it is in. Other companies like Phoenexia in the Czech Republic collaborate with the military to create speech analysis tools. They identify individuals by gender, age and stress levels and track them based on ‘voiceprints’. Blue Coat in the U.S. and Ipoque in Germany sell tools to governments in countries like China and Iran to prevent dissidents from organizing online.

Trovicor, previously a subsidiary of Nokia Siemens Networks, supplied the Bahraini government with interception technologies that tracked human rights activist Abdul Ghani Al Khanjar. He was shown details of personal mobile phone conversations from before he was interrogated and beaten in the winter of 2010-2011.

How Mass Surveillance Contractors Share Your Data with the State

In January 2011, the National Security Agency broke ground on a $1.5 billion facility in the Utah desert that is designed to store terabytes of domestic and foreign intelligence data forever and process it for years to come.

Telecommunication companies are forthcoming when it comes to disclosing client information to the authorities - no matter the country. Headlines during August’s unrest in the UK exposed how Research in Motion (RIM), makers of the Blackberry, offered to help the government identify their clients. RIM has been in similar negotiations to share BlackBerry Messenger data with the governments of India, Lebanon, Saudi Arabia, and the United Arab Emirates.

Weaponizing Data Kills Innocent People

There are commercial firms that now sell special software that analyze this data and turn it into powerful tools that can be used by military and intelligence agencies.

For example, in military bases across the U.S., Air Force pilots use a video link and joystick to fly Predator drones to conduct surveillance over the Middle East and Central Asia. This data is available to Central Intelligence Agency officials who use it to fire Hellfire missiles on targets.

The CIA officials have bought software that allows them to match phone signals and voice prints instantly and pinpoint the specific identity and location of individuals. Intelligence Integration Systems, Inc., based in Massachusetts - sells a “location-based analytics” software called Geospatial Toolkit for this purpose. Another Massachusetts company named Netezza, which bought a copy of the software, allegedly reverse engineered the code and sold a hacked version to the Central Intelligence Agency for use in remotely piloted drone aircraft.

IISI, which says that the software could be wrong by a distance of up to 40 feet, sued Netezza to prevent the use of this software. Company founder Rich Zimmerman stated in court that his “reaction was one of stun, amazement that they (CIA) want to kill people with my software that doesn’t work."

Orwell’s World

Across the world, mass surveillance contractors are helping intelligence agencies spy on individuals and ‘communities of interest’ on an industrial scale.

The Wikileaks Spy Files reveal the details of which companies are making billions selling sophisticated tracking tools to government buyers, flouting export rules, and turning a blind eye to dictatorial regimes that abuse human rights.

How to use the Spy Files

To search inside those files, click one of the link on the left pane of this page, to get the list of documents by type, company date or tag.

To search all these companies on a world map use the following tool from Owni

Monday, July 23, 2012

Screed of Momus: Is Neal Rauhauser an Informant?

Is Neal Rauhauser an Informant?

Neal Rauhauser
Neal Rauhauser, the Iowa native who came to prominence with his involvement in various online trolling efforts like the Beandog Milita, Twittergate, and Vile Tweets, has interesting associations.  Other sites, such as the Crying Wolfe Blog and Ron Brynaert's site, have publicized these associations in the past.  However, the media still has yet to take note.

As part of my continuing series on Neal Rauhauser and his involvement with various online hijinks, pranks, and slander campaigns, I've gone back into Neal's life as a Graettinger, IA native and former resident of Omaha, NE.  I've dug up two past marriages, and contacted various people in Neal's past for phone interviews.  And then there are the people whose lives have been affected by Neal over the past two years, people like blogger Mike Stack of New Jersey, who figured prominently in the revelation of Anthony Weiner's online tweets to porn stars and college aged coeds, including an infamous picture of his erection.

The story broke nationally through Andrew Breitbart, but Mike and his friend Dan Wolfe otherwise known as PatriotUSA76 broke the story with tweets. There is some dispute about how about they agreed to tweet, with Mike Stack saying that he was sent an email by PatriotUSA76 that clued him into a brewing sex scandal involving Congressman Weiner.  Mike Stack alleges that Dan Wolfe contacted him about Weiner after Stack left a comment about his Twitter avatar.  Wolfe pressed Stack to tweet the initial message related to Weiner's then rumored sex scandal, and said that he would re-tweet.  Stack did so.

What happened afterwards was simple enough: Mike Stack took the blame, and Dan Wolfe maintained his anonymity and disappeared.  And what a heavy blame it was: today, photos of Mike along with his arrest report from 2004 have been posted online, and he's been alleged to have framed Anthony Weiner by hacking his account.  Mike vehemently denies doing so.  However, his denials didn't register with the left wing tweeters who bombarded him with threatening tweets and emails.  They outed his address, photos of his home, and his work as a porn site moderator. Additionally, the 2004 case against Mike Stack was dropped.

But that's all been covered by other sites, and what's interesting to me is how Mike Stack managed to haul Neal into court by serving process on an attorney by the name of Mark Rasch.  Mark Rasch, for those of you who do not know, was the general counsel for the online vigilante effort that called itself Project Vigilant.  Project Vigilant was a loose conglomeration of hackers and infosec specialists that made waves when its founder, one Chet Uber, marched into Defcon to announce its existence and boast about the role Project Vigilant had in getting Pfc. Bradley Manning arrested.

Moreover, Mark Rasch is an attorney whose Washington, D.C. location just so happens to be in the same building with Baker & Hostetler, LLP, which happens to the same firm retained by Representative Weiner to investigate his possible hacked Twitter account.  Representative Weiner later admitted to his guilt, of course, but this did not stop some on the left from continuing to posit that he was set up.  It's hard to see how one can set a man up and make him tweet a photo of his erection to a woman on the other side of the country, but there are those who insist on believing in a grand conspiracy in the Weiner scandal that involved nefarious right wing bloggers.


Poulsen & Lamo
Rasch is also the former Department of Justice attorney who investigated Wired magazine's Senior Editor Kevin Poulsen for crime including mail and wire fraud, money laundering, and obstruction of justice. Facing seven counts, Poulsen received a mere 51 months in prison. And when he emerged from prison, where did he wind up shortly afterwards?  Security Focus, a publication that focused on security issues related to the Internet, a publication that just so happened to employ Mark Rasch.  What's stranger still is that Kevin Poulsen is now the Senior Editor at Wired, where he works with, you guessed it, Mark Rasch.

And what of Chet Uber, the Omaha resident who relocated to Florida and began accepting disability checks related to his diabetes and heart problems?  He founded Project Vigilant, a consortium of hackers and infosec experts that monitored 12 regional ISPs and turned over their findings to various government agencies.  Interestingly enough, while Project Vigilant's members insist they did not violate the law, one wonders why there is a need for Project Vigilant when the NSA has the capacity to monitor every bit of electronic communication throughout the world.

What's more, how does a man like Chet Uber get the money to found an organization like Project Vigilant, and how does he afford airfare to Defcon on disability checks that by his own account provide him less than $800 a month in income?  Here is Neal's explanation, from his post as Stranded Wind on Firedog Lake:

"I get periodic requests for help with network infrastructure problems, I had one come during the summer of 2009 that needed some special skills, and Chet answered some questions for me. It was a day’s work – $1,000 billed, and I had my customer make the check to BBHC Global so the company could afford to incorporate.


So that’s all there really is to it – a bunch of civic minded professionals who see each other at conferences, one of them on disability but wanting to volunteer so he could do something useful with his time, and one old friend repaying a debt to another by writing off a day’s consulting pay in hopes some good would come of it."

Chet Uber
According to Neal, he paid the incorporation costs for the company that financed Project Vigilant's emergence in the summer of 2009 by having his customer make out a $1000 check to BBHC Global.  Neal subsequently deleted his explanation of BBHC Global's genesis, but his fellow Firedoglake member shekissesfrogs had it saved in her cache and reposted it.  What's more interesting is how Neal had the time and energy to work a day and make $1000, but he didn't use that money to pay off his child support obligations.  At over $30,000 in the present day, Neal hasn't paid child support in a while.  At $675 a month, it's easy to compute his financial obligations to his children as stretching back to 2009.

His insistence that he didn't have the money because he could work is belied by his own version of events as to the rise of Project Vigilance and BBHC Global.  He paid the incorporation costs of BBHC Global with his work on a company's network infrastructure!  But it goes much further, as the following quote from Neal's Firedoglake post explaining how Project Vigilant came to be funded indicates:

"I hadn’t heard from Chet in quite a while. He’d had a massive heart attack in 2005, I got Lyme in 2007, and both of us were in pretty sad shape. I’d gone back to work at the beginning of the year and for a while my credit card was attached to his Walgreens account, covering meds he otherwise would not have been able to afford.

We started talking again, every week or so. A couple of times I logged in and paid his cell bill. He’d managed to hang on to a laptop through heart attack, losing a long term relationship, losing a business, and bouncing between friends and relatives. He finally qualified for disability and things started to get easier."


Neal had money to help pay for Chet's medications and even his cell phone bill, but he didn't pay the child support he owes for his children.  Despite insisting repeatedly to his ex-wife Nancy that he didn't have the money because of his Lyme Disease, by Neal's own account on Firedoglake he was working in the summer of 2009 and making enough money to pay for Chet Uber's medications and his cell phone bill!

Project Vigilant is a largely extraneous and even redundant group, given what we know about the NSA's capabilities, but the NSA, like other federal agencies, is occasionally constrained by obstacles like the law and procedural requirements.  And that, ladies and gentlemen, is where Project Vigilant becomes useful.  You have people like Neal Rauhauser, a man who allegedly hacked the computer of his ex-wife to be vindictive, working to penetrate 12 regional ISPs and monitor the information and behavior of their customers for the purposes of turning over that information to various federal agencies.  Neal has faced charges of criminal harassment from Mike Stack, the aforementioned New Jersey blogger who accused Neal of online harassment.

You have Neal's associates, like the various members of the Beandogs, represented by Neal to me in our communications last year as hackers. We know that one of those Beandogs, Sam Birbeck aka Methadonna, went on to infamy for his role in accusing HOPE: Preventing Euthanasia & Assisted Suicide director Paul Russell of retaining him for the purposes of rigging an online poll.  Birbeck sent emails saying that he would triple the agreed upon fee for his services. Trouble was, Paul Russell never retained Sam Birbeck for any job at all.

Sam Birbeck/Methadonna
But the supporters of the euthanasia bill in South Australia seized on the emails as proof of Russell's gaming of the polls that showed citizens overwhelmingly opposing the euthanasia bill.  One of the bill's supporters, a transexual gynecologist named Dr. Rosemary Jones, forwarded an email from another euthanasia advocate named Mark Lawrence which stated the following:

"Friends, from what I hear, they (the Canadian based colation [sic], with teh [sic] NCC SA as its Ausralian [sic] base) are paying small amounts of PayPal money to US gamers to rig these polls all over the world, 24/7- how very principled. That's how they got a 75/25 result on Adelaide Now on Tuesday, and, given that it is so obvious, why Adelaide Now at one point on Tuesday evening actually reduced the number of aggregate votes recorded. Good old NCC. Mark."

Isn't that a nice accusation, and isn't it consistent with the loser's limp and whining of Neal Rauhauser and other supporters of disgraced Representative Anthony Weiner?  Neal and his allies insist that Weiner was hacked, and that he didn't tweet the photo of his genitalia, even though Anthony Weiner accepted full responsibility for all of the tweets during his final his press conference.

And what we know of Brett Warren, aka @solaar of Maitland, FL, is that he too was linked to a robocalling operation in Canada in which he posed as Conservative Party aide Michael Sona to confess to Sona's involvement in the robocalling effort which led Canadian voters to believe that their polling places had been moved!  What are the odds that two known online associates of Neal Rauhauser would be involved in such tricks as they related to the political processes of two countries?

Just look at what Neal posted in his recollection of Project Vigilant's beginnings:

"We’d been into infosec stuff ever since we’d met, him (Chet Uber) much more than me, but this was the first time I heard the name Project Vigilant applied to his broad collection of associates. He began organizing with a will, herding infosec rock stars into formation, then pulling in those who wanted to learn. The names of those willing to be seen in public were detailed in the second Albertson column."

Did any of those who wanted to learn happen to be Beandogs or any of the other assorted trolls Neal was consorting with on Twitter during 2010 and early 2011?  Did Project Vigilant serve not merely as a means to surreptitiously make an end-run around legal restrictions on government monitoring of ISPs, but also a means of training the Beandogs and other like-minded partisan individuals in the skill sets necessary to perform the dirty tricks directed at conservative bloggers and libertarian tweeters we've seen over the past two years?

Or was it something even more nefarious, such as a shell game to provide a convenient narrative to cover for how the government came to be aware of Pfc. Bradley Manning's leak of classified diplomatic cables to Wikileaks?  What we know of Pfc. Manning's actions is simple enough: he isn't charged with leaking the cables online to Wikileaks. The government contends that he made a physical drop of disks to Wikileaks allies in the Boston area.  Why, then, would he communicate with the likes of a convicted hacker like Adrian Lamo, who in turn notified none other than Project Vigilant founder Chet Uber, who then notified Washington, D.C. attorney Mark Rasch, the man whose criminal investigation of Kevin Poulsen led to his conviction on seven criminal counts for which Poulsen received a surprisingly light sentence.

When you consider that before Adrian Lamo was involuntarily committed to a psychiatric hospital three weeks before he supposedly began communicating with Pfc. Manning, you begin to understand that something isn't quite right.  The government's chief witness against Bradley Manning is a man who has contradicted himself in numerous media interviews, and the main organization that helped bust Bradley Manning wasn't the NSA or any other U.S. intelligence agency, but was instead a group of infosec folks and hackers operating under the direction of a disabled man by the name of Chet Uber, who had to rely on Neal Rauhauser for his prescriptions, his cell phone bill, and the money to incorporate the company that served as the funding conduit for Project Vigilant.

And nowhere in BBHC Global's information is Neal Rauhauser listed as principal or even a member, even though he purportedly provided the startup money for BBHC Global. Instead, the owner of the BBHC Global domain name is one Steve Ruhe, who provides an interesting email: chet.uber@mac.com.  Steve Ruhe is a drywall contractor named R&R Drywall in Lincoln, NE.  Think of it: a drywall contractor who got into the information security business and registered BBHC Global's domain name under Chet Uber's mac.com account.  It strains credulity, especially when you consider that the domain name wasn't registered until April 2009.  The significance of this is tremendous, because we know from Wired Magazine's own reporting that Manning had been going through the classified information for months when he came across the infamous helicopter video in late 2009.

What if Project Vigilant and BBHC Global were merely shell organizations set up as part of a sophisticated operation to smoke out Bradley Manning?  And what if Bradley Manning's relationship with Adrian Lamo stemmed not from his leaking operation, but from his sexual orientation?  Adrian Lamo was a volunteer at PlanetOut during the mid-1990s.  PlanetOut is a gay and lesbian media firm. And given that Neal Rauhauser, the self-professed "old hacker" alleges that he fronted BBHC Global the money to incorporate with the proceeds from one of his jobs in the summer of 2009, what was his role in accumulating intelligence on the Manning leaks, if he had any role at all? And now that he is actively soliciting Anonymous and Lulzsec members and stirring up people at Occupy Wall Street, is he doing so in his capacity as a progressive activist or is he merely an informant passing on the information he accrues on social networks and IRCs to the federal government?  Surely the members of Occupy Wall Street and Anonymous would look at Neal's solicitous attitude quite differently if they were aware of his affiliation with Project Vigilance, its cooperation with the FBI and other various federal agencies, and the boast of its founder Chet Uber that his organization helped bust Bradley Manning.

What we know about Neal is that he is a self-professed Infragard member who has meetings with the FBI on occasion, and on May 30, 2011 Neal made the following claim on his blog:

"OK, kids, in addition to being a mouthy blogger I’m also an Infragard member and my day job gets me occasional meetings with the FBI. I just called the agent for my district who covers cybercrime and we need to get this muddle distilled down for him."

From what we know of the federal government and its history as it relates to movements like Occupy Wall Street, the anti-war movement during Vietnam, and the civil rights movement, planting people like Neal in those movements is not such a stretch.  COINTELPRO, anyone?  And given Neal's documented and notorious trolling of the Tea Party, and his repeated threats to refer various Tea Party supporters on Twitter to federal law enforcement, was his trolling an attempt at entrapment to provokeTea Party supporters on Twitter to engage in possibly illegal and threatening conduct with their reactions?

Considering that members of the Wrecking Crew like Jeannie McBride, who would later be outed as a registered Democrat, went on infamy for their cooperation with Neal Rauhauser, it would seem that Neal's operations were a good bit more than an effort to control the partisan narrative on social networks.   After all, how does the FBI allow a man with documented psychiatric issues like Neal Rauhauser to work even peripherally for a quasi-governmental initiative like Project Vigilance?  For that matter, given that their chief witness against Bradley Manning is Adrian Lamo, a man who was hospitalized for psychiatric issues three weeks before he came forward against Bradley Manning, things don't add up.

And considering that serving process for Neal in a criminal harassment case on Mark Rasch resulted in Neal showing up with Brett Kimberlin to Municipal Court, what is Velvet Revolution's role in Neal's possible activities as an infiltrator and informant?  We know that Velvet Revolution's financials are sparse, with little detail on how they've spent their substantial donations.  All we see of Velvet Revolution's expenditures are the various websites like Indict Breitbart and the alleged retaining of Neal Rauhauser to work on various tasks.  Is Velvet Revolution paying Neal Rauhauser, and if so, what services does Neal provide?  Are they appropriate for a registered non-profit with tax-exempt status?

And has the federal government paid Neal for services rendered in his capacities with Project Vigilant and Infragard, and if so, why hasn't Neal made an effort to address his financial obligations in Nebraska and Iowa?  Again, given the prior history of the federal government and the animus it has displayed toward alternative political movements like the civil rights movement, the anti-war movement, the Tea Party, Occupy Wall Street, and hacking organizations like Anonymous, LulzSec, and Wikileaks, it makes perfect sense to set a man with Neal's psychological and character defects loose in Zuccotti Park and on Twitter, where he can entice and provoke individuals into incriminating behavior that would compromise and discredit them and the movements they affiliate with.

For all of the questions related to Neal's involvement with Project Vigilant, Infragard, and his interaction with the federal government and his association with a former Department of Justice attorney whose protege and client have central positions in the Manning leaks and prosecution, one thing is very clear: those who are a part of Occupy Wall Street, Anonymous, and LulzSec, along with anyone in the Tea Party, should be very careful about what they say or divulge to Neal Rauhauser.


Author's Note: The reporting of Ron Brynaert, Crying Wolf Blog, The Other McCain, Liberty Chick, and various other bloggers and websites deserves to be credited for the extensive documentation of Neal's back history over the past two years.  Also, thanks to Brooks Bayne and his site The Trenches for their continuing dedication to this story.  To all of you who have read this series, thanks to you. There is so much more to come in the days and weeks ahead.  To Mike Stack, I owe you a debt of gratitude for the emails you sent.  It was like God dropped confirmation in my lap as to one of my theories.

MUST READ... more on this later...

^ed

Posted from DailyDDoSe

Saturday, June 30, 2012

Manage My Account - TwitterGate paper trail - "Catch me if you can?" Exhibit A

Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: Tumblr::API::AuthError
Next attempt in 4 days
4 days ago
Failed
Illuminati Terrorism
Reason: Tumblr::API::AuthError
Next attempt in 6 days
6 days ago
Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: Tumblr::API::AuthError
Next attempt in 7 days
7 days ago
Failed
DMs hacked: 6 months wiped (or so she th ...
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Twitter server unavailable ? Wanna bet?
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@srbijadanas, 12/29/10 3:00 PM me thinks ...
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 2:50 PM we saw too
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 12/28/10 6:44 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Conversation hiding the evidence ?
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@JasonBWhitman, 12/28/10 5:47 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@d_is, 12/29/10 4:39 AM another witness
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Conversation
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 1:33 AM you gave i ...
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:19 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:14 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@badjerry, 11/26/10 11:49 AM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@Dobroyeutro, 12/29/10 7:35 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Conversation @heyjude408 @safeworld4wome ...
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM now publ ...
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@papakelt, 12/29/10 6:37 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@yagbebi, 12/29/10 12:35 PM
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @JasonBWhitman
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl dm root
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@columbiajourn FYI -- hack3d
Reason: Tumblr::API::AuthError
Next attempt in 5 months
5 months ago
Failed
@columbiajourn FYI -- hack3d
Reason: Tumblr::API::AuthError
Next attempt in 7 months
7 months ago
Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: Tumblr::API::AuthError
Next attempt in 7 months
7 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @JasonBWhitman
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
@longhawl, 12/25/10 8:52 PM
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl dm root
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @JasonBWhitman
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
Authentication Error during attack
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
PWA Exposed disinfo provocateur & gang s ...
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
BlackBerry Meltdown: P@rANNOYED - DailyD ...
Reason: Tumblr::API::AuthError
Next attempt in 11 months
11 months ago
Failed
If the fed wants ya, they'll get ya. Per ...
Reason: Tumblr::API::AuthError
Next attempt in 12 months
12 months ago
Failed
Office of Legal Counsel: How Fraud & Abu ...
Reason: Tumblr::API::AuthError
Next attempt in 12 months
12 months ago
Failed
“The Roof is on Fire” and Philadelph ...
Reason: Tumblr::API::AuthError
Next attempt in about 1 year
about 1 year ago
Failed
“The Roof is on Fire” and Philadelph ...
Reason: Tumblr::API::AuthError
Next attempt in about 1 year
about 1 year ago
Failed
Elyssa Durant || NIRA Directory on Think ...
Reason: Tumblr::API::AuthError
Next attempt in about 1 year
about 1 year ago
Posted
@SpottyX, 12/29/10 8:39 PM
over 1 year ago
Posted
@rockingjude, 12/30/10 8:39 PM "loll"
over 1 year ago
Posted
12/30/10 5:16 PM @heywho #TwitterGate
over 1 year ago
Posted
Conversation
over 1 year ago
Posted
Conversation thread 2 #verified
over 1 year ago
Failed
Convicted Bomber, Neal Rauhauser, and Th ...
Reason: request error 403: Invalid token: Cannot parse AuthSub token: 2EjWUoceE5FCcQ3dZRZaYFF0EC72aKFF7EeP
Next attempt in 4 days
4 days ago
Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: request error 403: Invalid token: Token not found Invalid token: Token not found Error 403
Next attempt in 7 days
7 days ago
Failed
DMs hacked: 6 months wiped (or so she th ...
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Twitter server unavailable ? Wanna bet?
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@srbijadanas, 12/29/10 3:00 PM me thinks ...
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 2:50 PM we saw too
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 12/28/10 6:44 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Conversation hiding the evidence ?
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@JasonBWhitman, 12/28/10 5:47 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@d_is, 12/29/10 4:39 AM another witness
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Conversation
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 1:33 AM you gave i ...
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:19 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:14 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@badjerry, 11/26/10 11:49 AM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@Dobroyeutro, 12/29/10 7:35 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Conversation @heyjude408 @safeworld4wome ...
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM now publ ...
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@papakelt, 12/29/10 6:37 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@yagbebi, 12/29/10 12:35 PM
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl dm root
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
11:44 right on schedule
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@columbiajourn FYI -- hack3d
Reason: request error 403: Token not found Token not found Error 403
Next attempt in 5 months
5 months ago
Failed
@columbiajourn FYI -- hack3d
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 7 months
7 months ago
Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 7 months
7 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
@longhawl, 12/25/10 8:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl dm root
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
11:44 right on schedule
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Authentication Error during attack
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Odd Todd: Eyeball Hypochondria | Odd Tod ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
PWA Exposed disinfo provocateur & gang s ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
PWA Exposed disinfo provocateur & gang s ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
BlackBerry Meltdown: P@rANNOYED - DailyD ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 11 months
11 months ago
Failed
If the fed wants ya, they'll get ya. Per ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 12 months
12 months ago
Failed
If the fed wants ya, they'll get ya. Per ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 12 months
12 months ago
Failed
Office of Legal Counsel: How Fraud & Abu ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 12 months
12 months ago
Failed
“The Roof is on Fire” and Philadelph ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 year
about 1 year ago
Failed
“The Roof is on Fire” and Philadelph ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 year
about 1 year ago
Failed
Elyssa Durant || NIRA Directory on Think ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 year
about 1 year ago
Failed
Mind - When Parents Are Too Toxic to Tol ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 11/27/10 3:14 PM hacking @ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Charges dismissed against reformed-mob-b ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Police scandal in Philadelphia tips off ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Facebook conspiracy: Data mining for the ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@spademaccool @badjerry @heyjude408 @hey ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 12/30/10 8:39 PM "loll"
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
12/30/10 8:50 PM @longhawl || ACCOUNT S ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
12/30/10 5:16 PM @heywho #TwitterGate
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation thread 2 #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation thread 1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Facebook conspiracy: Data mining for the ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 11/27/10 3:14 PM hacking @ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
12/29/10 9:49 PM how to catch a cybersta ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
#E "hunting?"
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl dm root
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Stalked on Facebook too! New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@yagbebi, 12/29/10 12:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@papakelt, 12/29/10 6:37 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 6:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@firetown, 12/29/10 6:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 11/24/10 12:05 PM now publ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation @heyjude408 @safeworld4wome ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@Dobroyeutro, 12/29/10 7:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 9:16 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/29/10 8:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@HeyJude408, 12/29/10 9:54 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 11/28/10 2:55 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 10/17/10 9:13 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@badjerry, 11/26/10 11:49 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Excuses, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@wired, 3/9/10 8:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@q_pq look what i found 10/17/10 9:13 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@netlibertaire, 11/20/10 5:39 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@badjerry, 11/26/10 11:49 AM I knew
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@CelticFire69, 11/28/10 8:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/28/10 11:14 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/28/10 11:19 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@HeyJude408, 12/29/10 1:33 AM you gave i ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@d_is, 12/29/10 4:39 AM another witness
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@icpchad, 7/26/10 5:12 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/28/10 11:19 PM wanna talk i ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:21 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation too little too late. #verif ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@JasonBWhitman, 12/28/10 5:47 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation hiding the evidence ?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 12/28/10 6:44 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 12/28/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@rockingjude, 12/24/10 9:33 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/17/10 10:42 AM no second ch ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Mike Dammann (@firetown) @ElyssaD no mor ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@SpottyX, 12/26/10 5:20 AM @q_pq redirec ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@firetown, 12/20/10 11:42 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@firetown, 12/21/10 11:34 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@HeyJude408, 12/29/10 2:50 PM we saw too
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@srbijadanas, 12/29/10 3:00 PM me thinks ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
PWA Exposed disinfo provocateur & gang s ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Guilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Twitter server unavailable ? Wanna bet?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
DMs hacked: 6 months wiped (or so she th ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Evidence reveals hoax staged by @rocking ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Co-conspirators @rockingjude @longhawl # ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Illegal tampering of tweets? GTFO @rocki ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Authentication Error during attack
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Project World Awareness Disinformation A ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Papua New Guinea
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @d_is @rockingjude dm
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Disinformation agent exposed! Breaking !
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude get your paws ou ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude addtoany #verifi ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD using tweetdeck dupl ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude via @loghawl add ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude via add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude adtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD addtoany guilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD fire
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD @heyjude408 @thefeeg
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @uksmallbiz apparently not
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @gnudarwin 3rd party replies ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD #verified again #uk
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @SpottyX attacked through bot ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude she is using Twe ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude TweetDeck
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude add to any not v ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude via @longhawl us ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude now using TweedD ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude using TweetDeck ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude v @longhawl addt ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @uksmallbiz
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
ElyssaD sick. Twisted. map. #USA #VERIF ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet @Mtmk102 #USA #infosec alert
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @longhawl @rockingjude you ne ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Twisted
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
The Powers That Beat: ACCORDING TO EXPER ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Democrazy USA
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
BACKUP! Fwd: Tweet from @rockingjude ø� ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
400 Bad Request OMG!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
2010: The Year the Internet Went to War ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Wikileaks: This Is Just The Beginning | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
#CHAOS Chaos Computer Club & Wikileaks
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Gadgets Bring New Opportunities for Hack ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
RT @srbijadanas, 12/27/10 12:25 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Rule #1 @ElyssaD, 12/23/10 4:50 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Facebook
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Do Aliens Exist? If So, Will They Kill U ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Brits Release UFO Docs : Discovery News
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
No way Jose!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Rule #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@d_is, 12/17/10 11:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Hactivist Code of Ethics: RULE #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation passport
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@ElyssaD, 12/23/10 10:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@longhawl, 12/25/10 8:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
[Firetown.com] New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Twitter / Suspended [damn... i'm good!] ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
FULL TEXT ... @WIKILEAKS Sanity for Supe ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
First they Came for...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Wikileaks: Who Rules by the Code, Will F ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Untitled
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Former CIA Officials Admit To Faking Bin ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Rumor: Microsoft Working on New Windows ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
AirPlay Hack Streams Non-iTunes Video Be ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Sync Adds Voice Control of Smartphone Ap ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Google Buys Giant New York Building for ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Apple Bans Lame WikiLeaks App | Threat L ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Mobile Prison Guard Towers Coming to a W ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
The Reason I Stay
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Victims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Transaction Analysis: Conversation 12/17 ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Oh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Internet Crime Complaint Center (IC3) #N ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Internet Crime Complaint Center (IC3) | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
CYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
US Spying on its Citizens | via @FIRETOW ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Haiti/Chile EarthQuake H.A.A.R.P 2010 | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Social Security Fraud: Abuse of Process ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
"to help protect your privacy?" GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
TWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
TWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
TWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
TWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
George Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
When psychiatry tells you your kids are ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Hunger in America: Where are our taxes g ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Twitter / @Elyssa Durant: Check this vid ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Reality Bytes: Is Equal Opportunity Just ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
CyberBUSTED [Reality Bytes] 12/21/2010 0 ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
"to help protect your privacy?" GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Abscam Operation | Socyberty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
COINTELPRO targets [ listed under operat ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
How are you feeling today? @yagbebi, 12/ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
CyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Social Security Fraud: Abuse of Process ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Haiti/Chile EarthQuake H.A.A.R.P 2010 | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Rothschild daughter WARNS of bomb attack ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
US Spying on its Citizens | via @FIRETOW ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Wikileaks claims: US did find Iraq WMD | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
CYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Internet Crime Complaint Center (IC3) #N ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Oh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
CyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
George Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
redemption
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Operation Chaos #payback #FreE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
Location data
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in over 1 year
over 1 year ago
Failed
DMs hacked: 6 months wiped (or so she th ...
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Twitter server unavailable ? Wanna bet?
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@srbijadanas, 12/29/10 3:00 PM me thinks ...
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 2:50 PM we saw too
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 12/28/10 6:44 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Conversation hiding the evidence ?
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@JasonBWhitman, 12/28/10 5:47 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@d_is, 12/29/10 4:39 AM another witness
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Conversation
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@HeyJude408, 12/29/10 1:33 AM you gave i ...
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:19 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@ElyssaD, 12/28/10 11:14 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@badjerry, 11/26/10 11:49 AM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@Dobroyeutro, 12/29/10 7:35 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Conversation @heyjude408 @safeworld4wome ...
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@rockingjude, 11/24/10 12:05 PM now publ ...
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@papakelt, 12/29/10 6:37 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@yagbebi, 12/29/10 12:35 PM
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @rockingjude
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @JasonBWhitman
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl dm root
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
11:44 right on schedule
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
@columbiajourn FYI -- hack3d
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 5 months
5 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @JasonBWhitman
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Failed
Tweet from @longhawl
Reason: request error 400: Blog has exceeded rate limit or otherwise requires word verification for new post
Next attempt in 11 months
11 months ago
Posted
Tweet from @longhawl
11 months ago
Posted
11:44 right on schedule
11 months ago
Posted
@longhawl, 12/25/10 8:52 PM
11 months ago
Posted
Tweet from @longhawl
11 months ago
Posted
Tweet from @longhawl dm root
11 months ago
Posted
11:44 right on schedule
11 months ago
Posted
11:44 right on schedule
11 months ago
Posted
Tweet from @longhawl
11 months ago
Posted
Tweet from @longhawl
11 months ago

Posted from DailyDDoSe