Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20201017184611/https://github.com/brijeshb42/medium-style-confirm
mscConfirm("Delete","Are you sure you want to delete this post?",function(){alert("Post deleted");},function(){alert('Cancelled');});
mscConfirm(object) :
mscConfirm({title: 'License',subtitle: 'Do you accept the licese agreement?',// default: ''okText: 'I Agree',// default: OKcancelText: 'I Dont',// default: CanceldismissOverlay: true,// default: false, closes dialog when clicked on overlay.onOk: function(){alert('Awesome.');},onCancel: function(){alert('Sad face :( .');}});
New
Prompt -> Equivalent of JS prompt()
The API for mscPrompt and mscConfirm is same. Just the onOk callback of prompt receives a value parameter entered into the prompt.
mscPrompt(object) :
mscPrompt({title: 'Subscribe',subtitle: 'Enter your email to subscribe to the newsletter.',// default: '',defaultValue: 'email',// default: '', this value will be prefilled in the prompt box okText: 'Subscribe',// default: OKcancelText: 'Cancel',// default: CanceldismissOverlay: true,// default: false, closes dialog when clicked on overlay.placeholder: 'Enter your email',// placeholder value to show in input textboxonOk: function(value){mscAlert(value+" has been subscribed to the newsletter.");},onCancel: function(){mscAlert('Sad face :( .');}});
Alert -> Equivalent of JS alert()
mscAlert(text) :
mscAlert("Hello World.");
Added support for new lines and carriage return in mscAlert()
mscAlert(object) :
mscAlert({title: 'Done',subtitle: 'You have been registered successfully. \n Your reg. ID is 4321',// default: ''okText: 'Close',// default: OK});
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more