cyberanakinvader

@cybanakinvader

Hacktivist. May the force be with you. Anti ISIL padawan bot:

Starkiller Base
Joined February 2011
Born in 1996

@cybanakinvader is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @cybanakinvader.

  1. Pinned Tweet

    I will not be very active on Twitter though.

  2. May the force be with you.

  3. Uh, to strengthen my cyber "kung fu", it's time to go dark again.

  4. As said before, I won't conduct any hacking operations against Russia during the Olympics period.

  5. After this point, expect inactivity.

  6. Here's my new Wordpress blog:

  7. I bet that Erdogan will go full Palpatine after surviving a coup, though I can't determine which side should I support at this time.

  8. Switching to another topic, I am closely watching and monitoring the Turkey coup d'etat incident.

  9. meaning that only invited best buddies can join the social network, but even then, they have to try refraining from wasting server space.

  10. The social network will be far more exclusive than the Jester's court, due to server space limitations.

  11. Oh, forgot to tell you that I am emulating "The Jester" by setting up my own social network >>>

  12. My thoughts are with the families of the victims of attacks.

  13. Next, during my inactivity, I have heard about the terrorist attacks.

  14. Keep in mind that the KMRU/Nival dumps were scheduled to be released in today though, before I sped up the releases.

  15. I admit that I can't fully escape my urge to revenge against moskals even after KMRU/Nival dumps.

  16. But I have a petty revenge against the moskals nevertheless. After all the Olympics has not yet begun as of today.

  17. Those dumps are intended originally as an ultimatum, but ultimately I dropped that plan by released the dumps much earlier in March.

  18. Originally the KMRU/NIVAL data dumps are to be released on July 17 2016, which is today in relative to my time zone.

  19. Today is the 2nd anniversary of the MAS-17 tragedy.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.