The site has been under spam and DDoS attacks once again. Unfortunately I’m busy with other projects at the moment and can’t dedicate the time needed to make sure anonymous posts are still allowed while protecting against these attacks.
I have taken the site down for maintenance it will be back up within 48hrs. All existing snipts are fine and I will try to remove the trash that has made its way into the system. For the time being twitter login will be required to post until I get sufficient countermeasures in places to allow non-logged in users to post.
Sorry for the inconvenience, these spammers ruin it for everyone; and they are using TOR to further anonymize their attack. If you have any questions please tweet me.
We’re back online! I’m still monitoring the situation and there may be slight service interruptions later today as I further strengthen the DDoS protections that have been put in place. Thanks for your patience!
Snipt.org is currently undergoing a sustained DoS attack. No snipts or systems have been compromised someone just has too much time on their hands and I don’t have time at the moment to properly mitigate the attack.
The site will be offline for a few short hours, all services will be restored within 5 hrs. Sorry for the inconvenience, I will be researching ways to protect the site from these types of attacks in the future.
The patch is ready to go; but in a last second decision to give myself a safety net I decided to re-script a few things just in case something goes wrong no code is lost.
Everything should be good- data integrity and reliability is my top priority so I thank everyone for their patience as I ensure this is done correctly and reliably. I am doing my best to have the site up and running ASAP after I finalize the maintenance scripts to be nondestructive.
I am feeling the pain of the site being down as well as I use it to host my personal code and I use it heavily at work!
Thanks again for your patience, I’m trying to be as transparent and communicative as possible in this matter.
I’m pretty sure the maintenance patch is complete but it is very late here on the East Coast and my eyes are a bit bleary- so I’m going to wait til the morning to double check the patch and then roll it to the live site when I’m sure it covers all the issues I discovered during my audit.
Thanks again for your continued patience, @danosphere.
Tried to fire the site back up just now but the system was still experiencing issues. I’ll iron out the final issues and flip the switch back on tomorrow night, I can’t bring the site back online while this duplication bug exists; thank you for your patience.
As always, if there is critical code you need access to I can always directly access it for you while in a maintenance period- just tweet at me, @danosphere. I’m here to help!
Updates are taking a bit longer to than anticipated, we’ll be back online within 24hrs. Thanks for your patience.
*** STATUS UPDATE 1/9 @ 10:43pm EST ***
Another quick update, still working on the maintenance. Hoping to be back online ASAP. Possibly by tomorrow night at the latest. Sorry for the inconvenience while I work to resolve these issues. Thanks for your patience.
Currently performing some additional cleanup and maintenance during off-peak hours tonight. The site should be back up and humming tomorrow AM (Eastern Standard Time).
If you need immediate assistance I can be reached at anytime via @danosphere. Thanks for your patience as Snipt.org continues to mature into a stable, scalable code hosting platform.
You should now find that almost all of the spam on Snipt.org has been removed and it should remain that way. I will be working hard over the New Year’s holiday to add additional user-curation and reporting tools so that Snipt.org can really become a solid community repository for code.
Thanks for your patience, those spammers are nasty ones!