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

Advertisements

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

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
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

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
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

Wikileaks: This Is Just The Beginning | TheVirtualCircle

Wikileaks: This Is Just The Beginning

“An invasion of armies can be resisted, but not an idea whose time has come.”
 Victor Hugo

There is much agitation about Wikileaks on the chattering channels in
the US and elsewhere. The politicians are up in arms, many commentators are
aghast and the legal eagles are pontificating. The press is having a field day,
at least as regards the stories it can publish from leaked material. But
all of them seem to be missing the import of what is happening.

History is on the march.

There’s a strong analogy in this with the Diet of Worms and the doomed
attempt by Pope Leo X to silence Martin Luther.

Let’s eliminate some of the noise that is currently clogging the air.

  • The Julian Assange extradition to Sweden is almost irrelevant. It is
    generally perceived as an attempt to harass Assange and all it has done is
    provide him with a dramatic stage upon which to perform. The only relevant
    element in this is the fact that it has become global news.
  • The extradition of Julian Assange to the US will possibly make his life
    uncomfortable, but it will provide him with an even more powerful public stage.
    If it doesn’t happen the US government will be perceived as weak. If it happens
    it is unlikely to result in his conviction. If there’s no conviction it will be
    a victory for Assange and if he’s convicted, it will be an even greater victory
    for what he represents. For the US government, in terms of perception; it’s
    lose-lose-lose.
  • Julian Assange’s only importance is that of figurehead. If he’s pulled down
    from that position, by any event at all, whether it’s accidental, a conspiracy
    or the result of a legitimate recourse to law, it will not stop what has now
    started any more than finding Luther guilty at The Diet of Worms stopped the
    genesis of the Protestant movement.

The Battle That Was Lost

There was a brief attempt by the US government and its allies to try to
close Wikileaks down. If we think of this as an information war, then the first
battle in the war ended in a terrible defeat for the US. Here’s how it
went:

  • Wikileaks was hit by denial of service attacks. It quickly acquired enough
    mirrors to become invulnerable.
  • Commercial power was brought through PayPal, Visa and Mastercard to try to
    deny donations. This back-fired. There can be very little doubt that more money
    flowed to Wikileaks because of the use of that commercial weapon, and anyway it
    wasn’t fully effective. To stop such donations you’d need the co-operation of
    nearly every bank in the world.
  • Technical infrastructure power was brought to bear, with Amazon ejecting
    Wikileaks from their servers and EveryDNS revoking Wikileaks DNS registration.
    It wasn’t hard for Wikileaks to find another DNS and all that the Amazon gesture
    achieved was brand damage for Amazon.

Anything short of closing Wikileaks down was defeat, and the US government
went down to defeat in days. It was difficult, of course. The US Government
needed, for political reasons, to be seen to be doing something, so it did a few
ineffective things. Maybe more could be done.

The Lutheran Current

In war, if you don’t have a clear understanding of what
victory amounts to, you are in trouble. It is tempting to suggest that the US
government is in deep trouble for that reason alone. However, it’s a mistake to
see the US government as a specific side in this war. This is an info war and
info wars take place between power structures not countries. It’s the US
power structure, not the US itself, that currently has a side in this war.
Info wars are, by their very nature, civil wars between groups of citizens that
live under the aegis of a given information control structure. One side
wished to conserve it, while the other wishes to change it.

Martin Luther triggered an info war. On one side were power structures that
were based on controlling information in the way that it had been traditionally
controlled. On the other side were revolutionaries who believed that those power
structures needed to be replaced and information made more freely available than
before. The initial battle was over the Bible. The Roman Catholic Church in
Europe controlled the Bible. When printing presses appeared its control was
weakened. The Gutenburg Press began business in 1450, the Diet of Worms was 70
years later in 1521.

Following The Diet of Worms, Pope Leo X issued a “fatwa” proclaiming it legal
to kill Luther, but Luther simply retired to Wartburg Castle at Eisenach where he lived
incognito, but also protected, translating the Bible into German. And of course,
Luther wasn’t alone in translating the Bible. Others began to do the same.
The Catholic Church not only lost its monopoly on the Bible, it also lost
control of which language it was published in.

Nowadays, this doesn’t sound as big a deal as it really was.
At the time the Bible was regarded as the foundation of truth and knowledge.
Very few other books existed; just the Greek classics of Plato, Aristotle and
others. Those too were held in very high esteem.

Without the Protestant movement, Henry VIII of England would probably not
have dared to rebel against Rome and set up his own protestant Church of
England. Much later the English monarch, Charles I would be beheaded by the
protestant Oliver Cromwell. Europe quickly divided between Protestant and
Catholic countries, and the monarchies were gradually replaced either by
democratic republics or democracies that relegated their monarchs to figurehead
roles. The Diet of Worms had momentous consequences.

A War On Two Fronts

The US power structure cannot behave like the Soviet Union once did. It
cannot roll into Prague with columns of tanks and install a different government
by fiat. The Prague they seek to conquer is a virtual super-hydra. Strike it
down and a hundred identical mirrors rise up from nowhere. Even if you destroy
it entirely, other virtual Pragues will no doubt be established.

The infowar is now being fought on two fronts.

  1. The first front is the media itself, both old and new.
  2. The second front is the information technology that enables it.

In the Media

The ranks of the leaker-friendly side in this war are quickly growing in
number. Many professional journalists have stood up in Australia to protest
their government’s poor protection of Assange, its own citizen – and the public
seems to be on its side. Similarly a whole host of UK journalists have stood
shoulder to shoulder with Assange. Only in the US, where the press has become
remarkably docile, is there a shortage of Wikileaks support in the main stream
media, but this will change if the first amendment becomes the heart of the
debate – and it probably will.

Wikileaks is spawning imitators quickly. At the last count there were 7
infoleaks sites; BalkanLeaks in the Balkans, BrusselsLeaks in Belgium,
Indoleaks in Indonesia, Rospil in Russia, Tunileaks in Tunisia, Open Leaks
(a splinter from Wikileaks) and Wikileaks itself. Most of these sites have
mushroomed up in the past few weeks. There will be more.

It is likely that the idea of stealing information and leaking it “as a
public duty” has become viral. The number of actual leaks is likely to increase.
And this could spell disaster for any organization, government or otherwise,
that has inadequate information security and also has something to hide.
Information security was never a big area of investment for most organizations
and it clearly wasn’t a priority for the US Army. Many more embarrassing
leaks will occur from many places before any real semblance of information
security is common.

The tide seems to be running with Wikileaks. There are details in this
that ought to worry the US government if it is seeking to preserve any
semblance of the status quo.

  • President Obama promised openness in government but never delivered. Now
    he’s hoist by his own petard. The US government now needs to get to grips with
    the issue of transparency or to simply declare transparency to be undesirable.
  • Except for within-the-beltway-political-leaks, nobody leaks information to
    the US media any more. The US media is no longer trusted, because Wikileaks and
    organizations of that ilk are a “safer and sexier” place to leak to.
    Additionally, the US media appears to have lost the taste for investigative
    journalism.
  • The US media’s business models are failing. They are beginning to look like
    dinosaurs.
  • The US government is not the only target. Other governments are targets too.
    So are many large companies. The US indignation right now is because
    of the content of the diplomatic cables. But how will the US government
    handle the leaking of, say, banking information that indicates some fraud, or
    any corporate information that demonstrates back-door collusion with government
    or between other governments. Trying to shoot the messenger will not work well
    with those types of leak.

Information Technology

The attempt to close down Wikileaks revealed genuine areas of vulnerability
for Wikileaks and any other operation that wants to operate with impunity:

  • The DNS structure itself
  • Payment systems
  • Service providers (like Amazon)
  • Physical location

The very idea that US government can control the Internet for its own
ends is worrying to many people, not necessarily because of the present
situation, but because of situations that may arise in the future.

The natural reaction is to create a secure virtual infrastructure that makes
such action impossible. This is probably achievable with a series of technical
innovations. (Whether it is will determine the course of history) The
innovations would include:

  • A DNS based on peer-to-peer technology (which would be impossible to close
    by closing any node)
  • Physical mesh networks (so that it would be very difficult to disconnect any
    individual node).
  • Regularly encrypted traffic
  • Peer-to-peer payment systems (circumventing major clearing operations like
    Visa and Mastercard)
  • Cloud services (like EC2) that are anonymized

It would also require some minimal legal protection for such systems. That,
in turn, requires a government that will champion the kind of freedom that
Wikileaks seeks. Whether such a a government will step forward is hard to know,
but if any, Iceland is probably the candidate.

We will probably see such innovations come to pass – provoked by the
current confrontation.

It’s A Far Wider Conflict Than You Imagine

The infowar is real, but the protagonists are not as I have thus far
described them. The US may be sore right now with Wikileaks, but this is about
power structures. The US government is merely one of the power structures that
is under the threat of “looser transparency” Almost all governments are under
the same threat. Corporations that base their business models on corruption and
extreme lobbying are also under threat. It may even be that the current world
economic systems (national currencies and the world banking system) will be
challenged.

The last great info war was enabled by the introduction of printing. It
gave rise to a whole host of effects that were unpredictable at the time, but
logical in retrospect. Its revolutionary nature was not appreciated at all at
the time. However the following consequences can be laid at its door:

The schism in the Roman Church, the fall of the monarchies of Europe, the
rise of democracy; the introduction of paper money, modern banking, insurance,
limited companies, stock markets and other financial markets and much greater
international trade; the birth of newspapers, literacy, the publishing industry
and universal education.

This infowar did not begin with Julian Assange and Wikileaks, it began with
Tim Berners Lee.

The previous infowar did not begin with Martin Luther and his Ninety-Five
Theses, it began with Johannes Gutenberg.

Ultimately, it seems inevitable that other power structures will be drawn
into battles in this war: the governments of China, Russia and Iran, for
example.

http://www.thevirtualcircle.com/2010/12/wikileaks-this-is-just-the-beginning/

Gadgets Bring New Opportunities for Hackers – NYTimes.com

Researchers at Mocana, a security technology company in San Francisco,
recently discovered they could hack into a best-selling Internet-ready HDTV
model with unsettling ease.

They found a hole in the software that helps display Web sites on the TV and
leveraged that flaw to control information being sent to the television. They
could put up a fake screen for a site like Amazon.com
and then request credit card billing details for a purchase. They could also
monitor data being sent from the TV to sites.

“Consumer electronics makers as a class seem to be rushing to connect all
their products to the Internet,” said Adrian Turner, Mocana’s chief executive.
“I can tell you for a fact that the design teams at these companies have not put
enough thought into security.”

Mocana and firms like it sell technology for protecting devices and often try
to publicize potential threats. But the Mocana test also illustrates what
security experts have long warned: that the arrival of Internet TVs, smartphones
and other popular Web-ready gadgets will usher in a new era of threats by
presenting easy targets for hackers.

As these devices become more popular, experts say, consumers can expect to
run into familiar scams like credit card number thefts as well as new ones that
play off features in the products. And because the devices are relatively new,
they do not yet have as much protection as more traditional products, like
desktop computers, do.

“When it comes to where the majority of computing horsepower resides, you’re
seeing a shift from the desktop to mobile devices and Web-connected products,
and inevitably, that will trigger a change in focus within the hacking
community,” said K. Scott Morrison, the chief technology officer at Layer 7
Technologies, which helps companies manage their business software and
infrastructure. “I really do believe this is the new frontier for the hacking
community.”

To combat the threat, security companies have been pushing to develop new
protection models. They are promoting items like fingerprint scanners and face
recognition on devices, and tools that can disable a device or freeze its data
if an attack is reported. But so far, such security measures have largely failed
to reach the mainstream.

Enrique Salem, the chief executive at Symantec,
which makes antivirus software frequently installed on PCs, said it was unlikely
that his company would produce the same kind of software for all of the new
products. Such software can require a fair amount of computing muscle, which
would put too much burden on devices that lack the oomph and battery life of
traditional computers.

And second, the attacks that Symantec and others have seen on the devices are
so new that they will require a fresh approach, he said.

“With something like Android, it’s a different type of threat and it
functions differently,” Mr. Salem said.

Symantec will focus on fingerprint scanners and other personal identifiers to
devices, Mr. Salem said.

The company also hopes to use features in the devices to help with
protection. For example, if someone logs in to a computer from Florida, but
location-tracking data says that the person’s phone is in Texas, then an
application might ask a security question.

Another goal is to let consumers report a possible security problem and get
their data locked down or erased remotely until the problem is cleared up. “You
want that ability to wipe the data away if a device is lost,” Mr. Salem said.

The chip maker Intel
recently bought Symantec’s main security technology rival, McAfee, for $7.7
billion. Intel executives say they plan to build some of McAfee’s technology
into future chips that will go into mobile phones and other newer devices.

Cellphones have been connected to the Web for years, but for much of that
time, they tended to have tightly controlled, limited software and other
constraints that made it difficult for hackers to do much damage. Attackers
continued to find easier targets, and a larger pool of potential victims, by
going after PCs running Microsoft
Windows and other popular Web software.

But these days, smartphones have many more capabilities. And smartphone
shipments have hit a critical mass that makes them worth a hacker’s while.

Also, Apple,
Google,
Nokia
and others are in a race to fill their online mobile software stores
applications. These companies have review mechanisms that try to catch malicious
software, but the volume of new apps coupled with hackers’ wile make it
difficult to catch every bad actor.

With Android, in particular, Google has fostered a vibrant and chaotic
smartphone platform in which companies of various shapes, sizes and standards
have rushed out devices and complementary applications. Unlike Apple, Google
does not approve applications one by one.

Instead, it asks software makers to state what phone functions their
applications tap into and to present that information to consumers. People can
then decide if they are willing to download the application, and they can post
online reviews for the software.

A Google spokesman said that the company expected consumers to perform this
type of self-policing and added that Google quickly investigated applications
that received complaints.

Still, there is a Wild West vibe to the smartphone market these days as
smaller, unproven manufacturers have followed the likes of Apple, Nokia and Motorola
in making smartphones.

“The good smartphones have been pretty well designed,” said Mr. Morrison of
Layer 7 Technologies. “The problem now is the flood of secondary phones that
bring interesting diversity and also open up holes for hackers.”

Security companies have issued repeated warnings that hackers have already
started to capitalize on the application stores. The companies also caution that
and hackers have discovered fake
programs
that try steal passwords or make
expensive
phone calls.

Jimmy Shah, a mobile security researcher at McAfee Labs, said the company had
run into so-called smishing attacks, a variation on phishing, in which someone
is sent a deceptive text message that appears to have come from a bank or a
retailer. Often, the message will ask the person to call a customer support
line, at which point the attackers try to coax valuable information from the
victim.

Mr. Morrison said another concern was that hackers would concentrate on
trying to run up people’s phone bills or find ways to tap into the
location-tracking services tied to phones.

“It is like a stalker’s dream,” he said.

The flood of Web-enabled devices hitting the market, like the one the Mocana
researchers hacked into, may be a more immediate threat.

Mr. Turner of Mocana said the maker of that television had left crucial bits
of information about its security credentials and those of third parties in an
easy-to-reach spot, meaning that a hacker could infiltrate some of the data
exchanged between companies providing commerce services for the TV.

Mocana has notified the TV maker of the issues and has declined to reveal the
company’s identity in a bid to thwart hackers. Mr. Turner would say it was one
of the five best-selling Web-ready HDTVs.

“The things we found were mistakes that an inexperienced device designer
would make when connecting something to the Internet for the first time,” Mr.
Turner said.

Wikileaks: Who Rules by the Code, Will Fall by the Code

Wikileaks: Who Rules by the Code, Will Fall by the Code

by: Luis de Miranda  |  Liberation |
Op-Ed

The human being is an animal of protocol. Our behaviors –
whether consciously or not – obey codes. Until just recently, protocol was an
instrument of hegemonic power. The more one mastered the rules and their
construction, the more one controlled the population. The writing and policing
of protocols were the privilege of the dominant elites.

Today, the Internet is the site through which humanity is in
the process of realizing that freedom occurs by the collective reclamation of
the construction and reinvention of protocols. Wikileaks’ name will remain one
of the milestones of this democratization. In the word Wikileaks,
leaks is important: it is thanks to the leaks that the
decision-making circles which once appeared solid as rock liquefy and lose their
magnificence. But wiki is just as significant: it means that everyone
and anyone may contribute to this active demystification of protocols.

What do the Internet and diplomatic circles have in common?
They are two worlds governed by very strict protocols, but in opposite ways.
Diplomatic rigor is a surface varnish which enables every sort of hypocrisy, low
blow and betrayal underneath. Protocol is a stage set, while the action remains
in the shadow. The Internet’s rigor, to the contrary, is located in all that one
does not see: in its source codes, in its universal standards for program
writing and data treatment (for example, on the Internet, RFC standards, TCP/IP
or HTML). What is immediately visible on the Net is a joyous chaos, turpitude,
freedom of expression, all the manifestations of the human kaleidoscope. We have
long been more or less familiar with the codes which govern the more or less
muted life of embassies, those more or less tacit rules of etiquette, precedence
and relations between states and their emissaries. We are less familiar with the
recent operating logic of digital technology.

Wikileaks is the product of hacker culture. A hacker
is not some pimply miscreant who provokes the Third World war by fiddling around
with computers. A hacker is an actor in the real: his practice is based on
“reverse-engineering,” or retroconception. Which is to say? It’s a
matter of deconstructing the programs, the rules or the protocols constructed by
groups with a monopolistic purpose in order to understand how they are
engineered at the source, in order to modify them and become an actor with one’s
own communication instruments, if possible, in
open-source, that is, in conformity with the spirit of free
software, modifiable by all those who take the trouble to learn the protocols’
digital logic. However, hackers don’t limit this modus operandi to digital
programs: by dint of spending most of their time on the Internet, the younger
generations have by now totally absorbed algorithm. They know the extent to
which our worldly protocols, our political and social rules, our behavior, our
tastes, our beliefs and our identities have been constructed and are instruments
of control.

The diplomatic world, the world of the rulers, is certainly not
sacred. Many people have repeated in their analyses: the Wikileaks leaks are not
very surprising in their content. But let us not forget that “the medium is the
message,” according to Marshall McLuhan’s famous and still-illuminating formula.
The power of the historic event underway, of which Wikileaks is a particularly
potent manifestation, resides in its form rather than its content. This event is
called numerism. To wit, the global codification of our representations
into binary electronic sequences is a new universal DNA. This numerism, through
a contrast effect, brings evermore to light a complementary human tendency:
crealism, that is, the will to make oneself autonomous, to freely
eschew automatisms, all the while taking in hand a democratic re-creation of
protocols. In English, that’s called empowerment; in classical French,
capacitation.

Confronted with this double logic, the old elitist analogue
worlds of doubletalk and bluff – notably, those of politics and diplomatic
institutions – cannot but be rattled. The message Wikileaks, among others, is
sending to those who rule is the following: At present, you may resort to
digital logic to organize the world and control the masses; know that, like you,
the masses shall be able to access – like you – this universal protocol to
divert or unmask its uses for hegemonic ends. This democratization seems
inevitable, unless all those who know computer programming are to be put in
jail, a temptation some leaders, including in France, seem to be itching to
succumb to.

Who rules by the code, will fall by the code. Those who mean to
control the masses through biometrics and electronic control must expect to see
these digital protocols backfire thanks to the vigilance of some – provided the
Internet and the press remain free. A freedom must not be technical only, but
critical and constructive. Let us, along with Orwell, never forget that numerism
alone, in the absence of collective crealism, will not lead to more and more
democracy, but only to the best of all worlds.

Translated by Truthout’s literary editor, French translator
and sometime book reviewer, Leslie Thatcher.

http://www.truth-out.org/wikileaks-who-rules-code-will-fall-code66157