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!
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!
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!
Hey coders! It’s been far too long since my last post! The site update I talked about in my last post got slightly delayed because I have been torn between multiple simultaneous projects, but that’s no excuse!
As you may have noticed (and as @rbarr99 pointed out) Snipt.org twitter logins are down at the moment. This is because twitter has shutdown all support for its basic-authentication method (which is what Snipt.org) uses. No worries though, the new version of Snipt.org fully supports oAuth, something twitter has been encouraging, and something you guys have been requesting for quite some time.
The new site is mostly ready to rock. I am but one person, so I am sure there are bugs and things that may have slipped through the cracks, but I am hoping the community will work with me to point them out so that I can remedy them as soon as possible. I encourage you to use the feedback system to identify bugs and I will fix them ASAP.
This is just a heads-up. The new site will be rolling out saturday night (9.18.2010). I will post up with all the cool new features coming in the new release but for now I just wanted to keep everyone informed. All your embeds and snipt boxes will be fine, the only thing I am a little unsure about is the stability of the API in this release, but with your help I’ll get everything back to rock solid.
So keep your eyes peeled, and be expecting some downtime Saturday night as the new site rolls out. As always you can reach me anytime day or night on the twitter! Thanks again!
Hello friendly coders! It’s been a while since iI have touched snipt.org but I have some awesome news for ya! I’m back at it! For serious.
Big changes are on the way, all new things people have been requesting for quite some time, and even some new stuff! oAuth! IE support! Faster snipping!
It’s all coming, and soon. I am knee-deep in code right now refactoring the entire codebase to make a serious effort to take snipt to the next level. Hoping to rollout the freshly optimized site in 1-2 weeks from now and begin rolling out even more goodness shortly thereafter.
Spread the word, the Snipt.org machine is churning again, and soon it’ll be better than ever.
Stay tuned ;)
I have been informed people are having issues logging into Snipt.org today using their Twitter credentials. I’m working on fixing this and it should be taken care of in the next few hours. Just wanted to let everyone know I’m on it! #ServiceAlert
Update: The problem appears to have been on twitter’s end, login is working again! PS I am working on getting oAuth working now ;)
It’s been a while but I managed to sneak in some features people have been asking for using the feedback tab.
SniptBox RSS Feeds
Alot of people wanted to share the contents of their SniptBox via RSS, well now you can! All SniptBoxes are now equipped with RSS. You can grab the feed by clicking the RSS icon from your SniptBox homepage or via http://box.snipt.org/username/rss.
Snipt.org Wordpress Plugin 1.1
The latest version of the Snipt.org code embed plugin for wordpress is available on the wordpress plugin directory. This release now supports displaying your embedded snipts in the RSS feed of your blog.
Snipt View Counts
Now when you post a snipt you can see how many people have viewed it. This count is located in the bottom right corner of each snipt next to the share icons.
That’s all for now. There are still many more features on the way so subscribe to the RSS feed to stay on top of new updates. Thanks for using snipt.org!
Ok, so it appears the API was down after the server move, it is back up now. For those of you concerned with authorizing with the API via GET you can use this tool:
http://snipt.org/api/keygen
It will provide you a permanent token for the api based on your twitter credentials, to ensure your info is secure.
Upgrades are one the way. The current #1 is making the site fully IE7/IE8 compatible. Please note in the meantime if you are using IE you can switch to firefox/chrome/safari [all better browsers than IE] to utilize snipt.org. The site should be FULLY IE COMPATIBLE by the end of June ‘09.
I also want to add support for R/Splus as a language, if you are familiar with this language please contact me so I can add support for it!
Sorry for the delays everyone, we are a very small team doing the best we can to satisfy everyone’s needs. If you have something urgent you can reach me anytime day or night via twitter and I’ll do my best to get what you need done/fixed ASAP :)
In case you missed it Snipt.org was down over the weekend. This was due to an unfortunate oversight by our [now previous] hosting provider. I’ll post more on the story in the next day or two, after I’m sure I have all of our data secured.
In the meantime Snipt.org is back and running at full steam- on shiny new servers hosted by the good people at rackspace. Again my apologies for the outage, more info soon!
Hey! Hope everyone is enjoying all the new stuff we released last week. Over the weekend we changed a few things to continue our mission to make Snipt.org one of the best pastebins on the net. Thanks to @devmorgan we have updated the Snipt JS Embed to no longer use CSS IDs which he informed us was bad bad bad. Now it uses all CSS-classes so you may need to update your CSS :). Check out his awesome blog where he shares his developer know-how and even throws in some snipts for good measure.
Also big thanks to uber developer @dimebrain who let us know that the method-coloring of our themes wasn’t working at all! We got right on it and fixed it up, now you can view your method names in all the beautiful colors they were intended to be shown in! If you haven’t checked it out yet, you should see his very useful csharp library for interacting with the twitter API - tweetsharp.
If you find or have problems using Snipt.org tweet at me and I will get it fixed as fast as humanly possible. It’s through the help of users like you that Snipt.org has become what it is today!
