org.snipt.SniptBlog

Downtime-Migration - 12AM EST 09.09.2012 (3hrs)

Expect a small window of downtime tonight as I migrate all of Snipt.org to new hosting. The new hosting will provide for lower maintenance costs with higher, more rapid scalability options and a whole load of other cool resources.

The codebase, and DNS have already been migrated.

I will be shutting off the main site around 12AM EST, 09.08.2012 in order to migrate the database - the outage is planned for about 3hrs, and the site should be back up (along with all hosted code, embedded code, etc) by 3AM EST, 09.09.2012.

Thanks for the patience and the new hosting should provide for a much faster experience!

Minor Bugfixes Posted

Just pushed an update to the site addressing a few issues regarding the display of certain characters, and the “theme browser” not rendering correctly. Other minor backend unmentionables as well ;).

Enjoy. Please contact me directly with ANY problems: @danosphere

Up And Running!

Thanks to a nifty little article I’ve gotten everything back and running in far less than the anticipated 24 hours. Everything should be right as rain again, the theme browser page is not operational at the moment but will be restored tonight.

Thanks for your patience, no data/snipts were lost in the shuffle! :)

Downtime

Snipt.org will be experiencing downtime for the next 24hrs. Sorry for any inconvenienve this poses, all snipts and functionality will be restored after this maintenenance window.

Thanks for your patience!

Snipt 3.10beta Live!

I quietly rolled out Snipt v3.10b last night. Some of the changes include:

• Backend optimizations to make everything faster.
• Fixed some XSS gaps
• Added expansion memory- the snipt.org website will remember the state in which you prefer to view snipts (expanded or standard) and you can pass the state in the URL by simply adding #expand. 
• Added admin tools to help napalm spam
• Added the ability to recover deleted snipts within 30 days (requires admin assistance)
• Fixed a range of database indexing problems.
• The 3.0 API is ready, but I haven’t flipped the switch on it yet because I need to update the documentation.
• Fixed duplicitous v2-to-v3 migration on demand issues and cleaned up the duplicate snipts.

LOTS more coming, this is just more work shoring up the foundation and core new architecture now that Snipt.org v3 runs on a custom backend and has moved away from the Wordpress backend I was using to power v2 (albeit highly customized, it made the site slower than it needed to be).

Love hearing requests for new features, feel free to comment, visit the feedback section or tweet at me. Hope you enjoy the updates! Don’t forget to use a sniptbox to easily manage and secure your code!

Important Note: Major Migration Occurring 10.23.2011

Hello fellow code monkeys! It’s been a long, long time since the last update but I’ve been hard at work trying to make Snipt.org faster, scalable, and more reliable. What started out as a personal project/experiment in enabling code ubiquity is transforming into something bigger, and better and faster.

In order to ensure you’re most-valued code is not lost in the migration, please make sure to put any snipts you want to save in a SniptBox. The process is easy- simply login using Twitter, and then edit the snipt you wish to save. Check “add to SniptBox” and click the Save button. Please move all your snipts into a SniptBox by 10.23.2011 11:59PM to guarantee data integrity.

For those of you who have not used a SniptBox and no longer have the ability to edit your snipts- fear not, the new architecture should be able to migrate your snipt on-demand as soon as a request is made for it, at which point it will be “recreated” within the new architecture. Moving forward please consider using a SniptBox to manage your snipts- the SniptBox will become an increasingly central piece of the Snipt.org architecture, so long as your snipts are kept in a SniptBox they will never die (unless you kill them).

I’m really excited to be rolling out the new architecture, I’ll post once the move is complete. There will be a number of features returning that have been gone for a while, and there will be an select few features that will fall off temporarily as they are re-implemented in the new architecture, the new back-end has been rebuilt from the ground up! Thanks everyone for you patience with the sites performance and up-time, its about to get MUCH better!

“Recent” Page Temporarily Down

As you may have noticed, a lot is changing here at Snipt.org! The web UI is much better, the site is faster, and embeds have been optimized too! You may have also noticed that the “Recent Snipts” page is gone! I have taken it down temporarily as I work to cleanup and protect the site from spam.

There are some spam countermeasures currently in place, but for some reason the spam keeps coming! So I am working hard to put effective blockers in place to stop the influx of spam, and cleanup all the existing spam. After that cleanup is done, the “Recent Snipts” page will be back, and better than ever as it should be all code and no spam!

There is another post in the pipeline about everything that is new and awesome here at Snipt.org, and everything that is on the way, but I’ll share that with you once the spam issue is resolved.

As always, if you need to reach me I’m just a tweet away, and thanks again for supporting Snipt.org!

Slight Hiccup…

I attempted to roll the Snipt refresh to the live servers this weekend (as planned) but unfortunately the data migration ran into a snag and has forced me to postpone the refresh until I can properly port the existing data over to the new structure. 

This isn’t anything major, should be resolved in the next day or two. I’ll be posting here as updates are available. Just sit tight, sorry for any inconvenience!