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.
“And we are BACK! Thanks for your patience everyone. All the duplicate snipts should be gone, everything is backed up and the systems are running right again. If you have any issues pls contact me.”—Dan Wasyluk (@danosphere)
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.
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.
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!
“Snipt.org is once again running a proactive spam protection system. I’m working on blocking the tide of spam that has recently appeared on Snipt.org. Thanks for your patience as I weed out these bots and spammers.”—Dan Wasyluk, Founder (@danosphere)
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!
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! :)
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).
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!
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 @rbarr99pointed 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.
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!
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!
After a short feature-hiatus I’m proud to announce quite a few new things here at Snipt.org. As you may notice we have a sweet new jazzy logo provided by twitter user @miggi. We also have a well designed “extend” page which shows you all the cool new ways you can use Snipt (thanks to @wittyphrasehere).
As far as new features and things to play with there are quite a few-
- Change highlight theme on the fly
- Change text size on the fly via [+ / -] buttons
- Enabled/Disable word wrap
- Max / Min snipt pane (for easier viewing of large snipts)
Now your snipts can venture outside the walls of Snipt.org and take on a life all their own! The Snipt.org API allows you to access and modify snipts remotely via REST calls. You can also use the open sourceactionscript library to easily integrate the Snipt API with your Flash/Flex/AIR projects. To test the API and also make something cool, Snipt.org is now available on the desktop in a package I like to call the "Cloud Coder". This gives you easy access to snipping without having to launch a web browser, and best of all- its built on the brand new API. There are also other options, such as the new Wordpress plugin and the JS embed.
I hope you find these new features useful, Snipt.org is a tool for the community that is built on feedback from the community. If you have suggestions on how to improve Snipt, just shoot me a tweet!
Sharing code on twitter is a great way to collaborate using Snipt.org, but what if you could discuss the code right the site itself? Now you can.
All Snipts now support commenting, proudly powered by DISQUS :). To start collaborating just click the “comments” link in the bottom right hand corner of any Snipt. Comments can be used as a powerful tool, use them to collaborate, to ask questions, or to post corrections. Whatever you do with them, make sure you have fun!
You may find a few new things on Snipt when you go to share your code today. There is a new “min/max” feature which will allow you to maximize the width of the code pane to fit more code without scrolling.
If you keep a Snipt Box here you can now browse your box by category, making it easier to quickly find the code you need.
Just rolled out some new features to Snipt, and thought I’d stop by the blog and fill you in! Here is some new goodness for you to play with:
Edit / Delete Snipts
Yes you can finally edit and delete your snipts- and you don’t even need to login! You can edit snipts for 30days without twitter login and with login you can edit them… forever!
If you haven’t noticed… you can rate snipts- if its good code, vote it up, if its bad, vote it down. You can now see the top 10 highest rated snipts here.
More Twitter Integration
There is now more twitter integration to Snipt. You can actually login at anytime using your twitter username and password to easily edit snipts in your snipt box. Also, snipts saved to your snipt box will have a link back to your twitter profile. Embedded versions of the snipt have also been updated to link back to the snipt itself rather than the snipt.org homepage.
Also added some more themes! I’ll be adding more throughout the week…
There are still more features on the way, stay informed via our RSS feed to get up to the minute updates.
The Snipt embed is a powerful tool- it lets you share the code you store here on Snipt.org in other places- like on your blog or on another website. The embed is much more than a simple script though- it is a highly stylable and customizable embedded item.
There are two major styling aspects to the Snipt embed, the container, and the code. Both are fully customizable. In this post I’ll explain how to make the most out of the Snipt embed.
If you applied a theme to this snipt, it would show up embedded with that theme, but even themes can be overriden for maximum flexibility.
The embed container is styled using CSS. This can be modified by overriding the default CSS styles. You can use the Snipt embed CSS Template to get started. Just paste it after the embed script and your ready to get styling.
By simply playing with some of the css you can completely change the appearance of the embed. Here are just a few examples, click view source to see the styles that create this effect:
As you can see you can use CSS to change everything about the embed. This is just a small example of what you can do with CSS and the Snipt embed.
But what about the code highlighting itself? Yep, you can change that too.
In addition to CSS you can pass the embed parameters to change its appearance on the fly. The embed takes 3 (optional) parameters-
Font Size (fontsize)
Here is an example: <script src=”http://embed.snipt.org/sok/font=arial&fontsize=12&colors=000000,000000,000000,000000,000000,000000,000000,000000,000000”></script>
Creates an embed like this. As you can see the font is now Arial size 12, and all the code is black because we have set all the highlight fields to black (000000). The widget takes 9 hex based colors, numbers only, comma seperated. Any colors you do not pass will be replaced by the default or the theme color if your snipt uses themes.
The color values are, in order:
OVERALL COLOR VARIABLE COLOR KEYWORD COLOR METHOD COLOR COMMENT COLOR STRING COLOR NUMBER COLOR SYMBOL COLOR ESCAPE CHAR COLOR
The goal of the Snipt embed is to make sharing code easier- not only that but to be able to share it in whatever motif you want. If people desire even MORE flexibility I will gladly extend the embed, just tweet at me or post in the forums.
There are some new features on Snipt that you might not have seen! Here’s a quick roundup:
Themes! There is now an extendable library of highlighting themes for your code here on Snipt- check it out in the themes section. Do you want a theme you don’t see in the library? Just tweet at me and I’ll add it. These themes will be reflected in embedded versions of the snipt, but can be restyled in the embed as well.
Download Snipt / Raw Text Snipt You can now download snipts! Just click the “download” link at the bottom of the snipt. All the popular languages will be downloaded in the target language (.php, .c, etc). If you just want a quick way to grab the snipt click the “raw text” link at the bottom of the snipt and a new window will open with the raw text of your snipt (unhighlighted).
I will be posting an extensive styling guide on how to use the embeddable snipt in the next few days, you can change it to fit any color theme and even make your own!
Just a small update this time. The Snipt code editor has been upgraded with more robust tabbing support! You may also notice some more descriptive error messages to give you a better idea of whats going on when Snipt runs into problems. Thanks to twitter user @billnega for his valuable feedback!
Additionally we have added “language memory” to the Snipt code editor so you don’t have to reselect your language every time you add a snipt. You can thank twitter user @mp3tricord for this one.
Do you have ideas or suggestions? We do our best to implement user feedback ASAP (usually within hours). Shoot your feedback to us via twitter, or on our user feedback system.
I’m happy to announce you can now embed your Snipts! Just click the “Embed this Snipt” link at the bottom of your Snipt, you will get a short <script>, this will allow you to embed your Snipt anywhere you want! Just copy paste the code into any HTML form!
Styling the Embed
In addition to embedding Snipts you can also style the embed container. Here are the stylable elements (widget, snipt title, snipt language, header, code container). They can be controlled by overriding the style names below AFTER the embed code:
To change the font size of the formatted code you’ll need to add ‘&fontsize=18’ (changes font to 18px) to the end of the embed src. The default fontsize is 12px.
Here are the default values for the embed styles, remember for your stylings to take effect you need to override these CSS ID’s after the embed tag.
That’s it, your ready to start sharing your Snipts with the world! Please remember this is BETA. If you have any problems at all please tweet@me or post to the feedback forums.
Thanks everyone for all the support shown towards Snipt.org! I’m glad
people are using this thing, and as such, have added some new features:
Snipt Box allows you to easily retrieve code that you snip. It uses your
twitter info to create a ‘Snipt Box’ just for you. To use Snipt Box just check
“Add to my Snipt Box” from the homepage. You can always access
your box via http://box.snipt.org/twitterusername.
Got a Snipt you don’t want to show up in search results? Just check
the “private” checkbox on the homepage and your Snipt will be
hidden from search, but it will still show up in your box.
As always you can still post Snipts without your twitter data, just
leave the “Save to my Snipt Box” option unchecked.
Thanks again for all the support, hope the community finds these tools useful!
Snipt is a tool for developers and non developers alike. It allows you to post long pieces of text or code (Snipts) and share them with people using convenient short URLs. This is useful for things like Twitter and Instant Messaging where being concise is key.
Snipt supports over 125 different formats ranging from csharp and actionscript to plain text and ascii. We are constantly adding formats to support the growing community. Need a new format? Please let us know!