Shutdownify

From Archiveteam
Jump to navigation Jump to search
Shutdownify
URL https://www.shutdownify.com
Status Offline
Archiving status Unknown
Archiving type Unknown
Project source shutdownify-grab
Project tracker shutdownify
IRC channel #archiveteam-bs (on hackint)
(formerly #dash-h-now (on EFnet))

Shutdownify is shutdown notice as a service startup. Shutting down December 31 2015

Shutdown

Shutdownify is shutting down

It is with tremendous regret that I must announce the shutdown of Shutdownify.

I'd like to thank our users for allowing us the chance to serve you during what was often a very difficult time in your professional lives. I would also like to thank our employees for their dedication and our investors and advisors for their support.

All of your existing shutdown notices can be exported from the Control Panel.

Shutdownify's last meal is its own dog food.

How can I help?

Enumerating hosted shutdown notices

We need a list of all shutdown notices hosted by this site. Also, are there forums or other user data to archive?

Update: No forums apparently. But I could be missing something... --colMustard

Update 2: Shitdownify lacks a list of hosted sites. Assholes. We tried to find a database ID to cycle, but no luck yet. Possibly google for their asinine shutdown templates? Or, get Sketchcow to apply pressure on social media? --anon1031

Update 3: Built a list of shutdown notices by getting a list of all YC startups thru 2015, and cross-referencing with current startup list. This list may be incomplete. Recommend Archiveteam Warrior supplement this with marcov-chain-generated startup names based on /usr/dict/words (ie, flicker -> flickr.com; special -> special.ly etc). --closure

Running a Warrior

You can start up a Warrior and there select Shutdownify. (If you don't really care what you are archiving, select ArchiveTeam's Choice instead, as at some points ArchiveTeam may prioritize another project.)

Running the script manually

If you use Linux and you're a bit familiar with it, you can try running the script directly.

The instructions can be found at github.com/ArchiveTeam/shutdownify-grab.

Some additional information
Don't forget to replace YOURNICKHERE with your nickname.

The number after --concurrent determines how many threads run at the same time. You can increase this number if your resources (RAM, CPU, bandwidth) are sufficient. However, if you constantly see messages about rate limiting, there is no need to increase the concurrency.

If you want to stop the script, please do it gracefully if possible. To do so, create an empty file named STOP in the folder of the script (terminal command: touch STOP). The script finishes the current item(s) and stops only after that. (If you kill the script immediately, the items get broken, and they will need to be reassigned to another user.) – Before starting the script again, don't forget to remove the STOP file.

If you see "Project code is out of date", kill the script, go to its folder (cd shutdownify-grab) and issue git pull https://github.com/ArchiveTeam/shutdownify-grab. After the updating has finished, re-launch the script.

Donating to the Internet Archive

Content downloaded by the ArchiveTeam will be uploaded to the Internet Archive, where it will be stored and be available – hopefully – forever. However, storing it costs thousands of dollars in the long run. So, if you can afford, please consider donating to the Internet Archive, so that this piece of history can be kept for us all. http://archive.org/donate

Do you like our cause?

If you want to help in other projects, want to learn more about ArchiveTeam, or even help in development in general, navigate to the Main Page of this wiki, from there you can reach a lot of information. The Team consists of volunteers working on the projects in their free time, so helping hands (and resources) are always welcome.

Archives

References


External Links