Advertisement
Guest User

Closure of Bugabuse.Net in 20 days from this post

a guest
Jan 26th, 2015
533
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.74 KB | None | 0 0
  1. In 20 days, bugabuse.net will close its doors.
  2. Announcement:
  3.  
  4. (Perhaps temporarily) Closure of BugAbuse.Net
  5. Dear Users,
  6.  
  7.  
  8. Since the inception of Bugabuse.Net in 2010, it has been a joy for everybody involved, to run.
  9. Through the thick and the thin, the DDoS attacks, the hackings, and the fun, we progressed.
  10.  
  11.  
  12. 42,695 Threads
  13.  
  14. 353,124 Posts
  15.  
  16. 32,085 Members
  17. That is our stats. And it will no longer go any higher.
  18.  
  19. A bit of history about BugAbuse:
  20.  
  21. When HaxUnit first started the forum back in 2010, it was an initiative to open the community of those that were interested in the not-so-legit side of RuneScape.
  22. Glitchers, Bug-Abusers, and more.
  23. Through advertisements on the HaxUnit channel, it thrived.
  24. With 200+ members on at a single time, there was never a dull moment.
  25.  
  26. Eventually, a hacking section was added, and "recovery" started to boom.
  27. The technique known as recovery, being used on RuneScape, was not new to those at BugAbuse, however.
  28. Likely starting on the website G4HQ, users such as k0m4, bar~, and trick, would showcase their recoveries with no databases used.
  29. Purely using Google to find a username, they would guess previous passwords and creation dates, and send off a request. They were commonly accepted.
  30.  
  31.  
  32. With the re-release of free trade on RuneScape, those interested in making money through "hacking" flocked to BugAbuse to acquire the skills. With a helpful community and a large amount of resources, it was a newcomers dream.
  33.  
  34. The admins tried to keep the place safe, recruiting moderators such as TOXSIN, and Alex_J_Leon[at the time] to keep the community safe from scammers, and other harms.
  35.  
  36. Eventually, around April of 2011, Bugabuse was hacked.
  37. The sys-admin at the time, Iceforg, did not have the skill [at the time] to understand the hack, or recover from it.
  38. Major mistakes were made in regard to the hack, such as re-use of passwords on other websites, backdoors left in the website and other problems.
  39. Eventually, it was time to shut the website down. The team, Iceforg, Hej, Quint, Fluid Karma, and Roy, left a "thank you and goodbye" message on the Bugabuse.Net page.
  40.  
  41. And then Bugabuse.Net was no more. At the time, there were no alternatives.
  42. For months, requests came in asking for the re-opening of BugAbuse, but were denied.
  43.  
  44. Then, in July 2011, Quint, Toil(Known as GitHub at the time), and Hej, performed the now infamous, "Rotten Potato Incident".
  45. Quint and I set up Mod Chrisso in a way that Chrisso teleported to Quint, who was waiting in the "Stealing Creation minigame.
  46. Once inside, Quint was able to pick-pocket the Rotten Potato from Chriso, and leave the minigame.
  47. With this, we waited. We had a recording, but didn't want to publish it.
  48. Until August, we did nothing. But, early August, Chrisso banned Quint's account, enraging both Toil and Quint.
  49. We planned to release the video, along with re-opening BugAbuse.Net. It was an uphill battle to reopen BugAbuse, since we had to secure the domain, and set up everything accordingly.
  50. And that is the origin story of BugAbuse.Net.
  51.  
  52. The rest, as they say, is history.
  53.  
  54.  
  55. From there, BugAbuse once again thrived. With the addition of new features, the community was happy.
  56. Throughout the life-span of Bugabuse, incredible things have been achieved. Things that could not have happened anywhere else.
  57.  
  58.  
  59. Sadly, however, all good things must ome to an end. And that is what this is.
  60. "You either die a hero or you live long enough to see yourself become the villian"
  61.  
  62. And that's what I must not allow. BugAbuse must die an honorable death.
  63.  
  64.  
  65.  
  66. Therefore, I am closing BugAbuse.
  67. It has been a great run, and everybody has been great.
  68.  
  69. The skills acquired on BugAbuse could not have been found anywhere else, which is why it was so unique.
  70.  
  71. And without every single one of you, it wouldn't have been possible.
  72.  
  73.  
  74.  
  75. From everybody at Bugabuse.Net, to everybody at Bugabuse.Net, I say: Have fun, Good luck, and Thank you.
  76.  
  77. Will BugAbuse return? Who knows. If enough interest is made in the future, it may be possible.
  78.  
  79.  
  80. For the future, I release this backup of the bugabuse.net server: dump-BA.tar.bz2.gpg(2.1gb) (PM's are wiped, IP's are wiped, and passwords are wiped)
  81. It contains everything needed, including a database dump, to start a bugabuse.net for yourself.
  82. It is encrypted using GPG, with an encryption key that is stored off-site. If required, it will be decrypted.
  83.  
  84.  
  85. For those interested in iLookup, contact me. I'll arrange something.
  86. For contact: [email protected] (email)
  87.  
  88.  
  89.  
  90. Posting has been closed, and <b>new</b> subscriptions have been disabled. BA is now "read-only", except for the following components:
  91. dblookup,
  92. ilookup
  93. shoutbox.
  94.  
  95.  
  96. In 20 days from this post, everything will be removed, and replaced with this text.
  97.  
  98. Goodnight, sweet prince.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement