nyuuzyou/wikis huggingface dataset:
Deploy OVA to VMware ESXi

== Convert OVA to OVF ==
Download OVF tool from VMware site (requires VMware account).
Install the OVF tool.
Open PowerShell.
Run:
 ovftool.exe --lax <OVA file> <OVF output file>
Example: 
 PS C:\Users\warrior\Downloads> & "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --lax .\archiveteam-warrior-v2-20121008.ova warrior.ovf
Open warrior.ovf with your favorite text editor. It's XML.
Search:
 <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
Replace to:
 <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType> 
Search:
 <Item>
 <rasd:Address>0</rasd:Address>
 <rasd:Caption>sataController0</rasd:Caption>
 <rasd:Description>SATA Controller</rasd:Description>
 <rasd:ElementName>sataController0</rasd:ElementName>
 <rasd:InstanceID>5</rasd:InstanceID>
 <rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
 <rasd:ResourceType>20</rasd:ResourceType>
 </Item>
Replace to:
 <Item>
 <rasd:Address>0</rasd:Address>
 <rasd:Caption>SCSIController</rasd:Caption>
 <rasd:Description>SCSI Controller</rasd:Description>
 <rasd:ElementName>SCSIController</rasd:ElementName>
 <rasd:InstanceID>5</rasd:InstanceID>
 <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
 <rasd:ResourceType>6</rasd:ResourceType>
 </Item>
Save the .ovf file.
== Deploy OVF to VMware ESXi ==
Open the ESXi web interface UI.
Go to Virtual Machines. Click Create / Register VM. Select Deploy a virtual machine from an OVF or OVA file. Click Next. Give the virtual machine a name. Drag'n'drop or select the .ovf and .vmdk files. Select NIC. Click Finish. Wait ESXi to deploy the image. Open the console to see the HTTP address where the warrior is running. Go to the address and join the team!
Designer News

Designer News is a social news website like Reddit for design and technology professionals. Owned by LayerVault, which is shutting down on April 11, 2015. We grabbed a copy of it on April 11, 2015 as part of our LayerVault grab.
== Site structure ==
*https://news.layervault.com/u/21791 (user)
*https://news.layervault.com/stories/10831 (story)
**https://news.layervault.com/click/stories/41736 (redirect)
*news.layervault.com items are numeric, sequential
Desura

Desura was an alternative video game distribution platform, similar to the likes of Steam but some games on the site were DRM-free.
In June 2015, Desura's parent company Bad Juju Games filed for bankruptcy. In October 2016, it was announced that Desura had been acquired by OnePlay. The website is offline since October/November 2016 (according to Wayback Machine) and a new game distribution platform is to be put up in place by OnePlay in "first quarter of 2017".
In June 2020, the website returned with an "opening soon" announcement for "a convenient platform for you to enjoy all your favorite online games in one place". According to a thread on Reddit, the site is now owned by a Russian guy trying to build a Flash game hub.
== See also ==
Files of the installed, original Desura client
== References ==
Category:Video games
Dev/Infrastructure

The Archive Team infrastructure is a distributed web processing system used for distributed preservation of service attacks.
== Component Overview ==
Figure	Description
1 	Website in Danger
2 	Warrior
3 	Tracker
4 	Upload Target
5 	Internet Archive
=== Website in Danger ===
The website in danger is typically a website exhibiting combinations of 
* acquihire
* mass layoffs
* neglect, decay, unhealthy, or owners missing in action
* political and legal issues 
* robots.txt exclusion file that forbids crawling by Wayback Machine (whether intentionally or unintentionally)
* cultural significance
=== Warrior ===
The Warrior is client code run by volunteers that grabs/scrapes the content of the website in danger.
Websites often implement throttling systems to protect themselves for various reasons such as spam or server load. Typical systems use IP address bans. As such, many Warriors, running on many IP addresses, are needed.
Content is usually grabbed and saved in WARC files.
=== Tracker ===
The Tracker is server code run by "core" Archive Team volunteers. The Tracker assigns what the Warrior should download and provides a leaderboard.
=== Upload Targets ===
Targets (sometimes called "staging servers") are typically servers running Rsync run by "core" volunteers. Warriors upload WARC files to these hosts. The hosts queue and package up the WARC files into large WARC files (Megawarcs). Then, the Megawarcs are uploaded to the Internet Archive under the collection.
=== Internet Archive ===
The Internet Archive is a digital library and archive. It is different from other hosting services because they are not a distribution platform. If there is an legal issue, items are "darked" (made inaccessible to the general public) instead of deleted.
An item is ingested by the Wayback Machine if it
* has .warc, .warc.gz. or .warc.zst files,
* has a "web" media type,
* and is under the Archive Team collection.
Dev/Project Management

Successful projects result from excellent project management.
* ProTip™: Appoint roles, delegate responsibility, manage resources, and listen to fellow volunteers.
== The Flight Crew and Customers ==
Flying an aircraft—even for a single journey—requires collaboration and cooperation. An Archive Team project is very similar:
=== Pilot ===
* mediates issues
* adds items to tracker queue
* monitors for buggy results
=== Co-pilot ===
* writes content grab scripts
* answers technical questions
* takes the role of pilot if the pilot is missing in action
=== Engineer ===
* admins the tracker host machine
* sets up GitHub repository permissions
* set ups Rsync hosts
=== Attendants ===
* answers general questions
* troubleshoots installation problems
* triage bugs and issues
=== Hat-Wearing Loudmouth ===
* wears hats
* a loudmouth
* over 1 million followers for his cat's Twitter account
* named Jason Scott 
=== Passengers ===
* runs Warrior VM appliance
* runs scripts manually
* have many IP addresses
* future potential pilots
* submits GitHub pull requests
Dev/Source Code

Fork me on GitHub! File and triage issues, fix bugs, refactor code, submit pull requests… all welcome! Discussion in .
See this link for all issues.
The warrior uses the following repos:
== Client code ==
Client code includes code that the Warrior executes.
;warrior3 - bootstrap and tools to build the image
:Bootstrap code that is pulled from GitHub by the appliance and starts a docker container
;archiveteam/warrior-dockerfile - the container
:Instructions to boostrap the docker container
;warrior2 - warrior runner code
:Main code that runs inside of the docker container
;seesaw-kit'''
:Library that helps build grab scripts, the web interface, and pipeline engine for the warrior. The name "seesaw" comes from its original behavior: download, upload, and repeat.
=== Projects ===
Projects are in separate repositories typically with the name -grab as a suffix.
Item lists that are loaded into the tracker are sometimes saved into a repo with -items as a suffix. Scripts to build searchable index HTML pages are usually suffixed with -index.
== Server code ==
Server code includes code that the Tracker executes.
universal-tracker - Ruby
:The server of which the Seesaw contacts
warrior-hq - Ruby
:The server of which the warrior appliances contact for project metadata
archiveteam-megawarc-factory - shell
:The scripts that bundles the WARC files.
=== URLTeam code ===
URLTeam code is independent from the tracker and warrior.
Old:
tinyback
: The client code that scrapes the shortlinks. It includes a pipeline shim to run the code.
tinyarchive
: The server code for the tracker.
New:
terroroftinytown-client-grab
: A pipeline shim to run the code.
terroroftinytown
: The code for both the client library and tracker.
== Misc ==
warrior-dockerfile
:Dockerfile that runs the warrior inside a Docker container.
ArchiveBot - Ruby, Python, Lua
:An IRC bot for archiving websites.
wget-lua - C, Lua
:A patched version of Wget for web crawling.
standalone-readme-template - Markdown
:A template for readme files included in grab repositories.
archiveteam-dev-env - Shell
:Ubuntu preseed for a developer environment for ArchiveTeam projects.
wpull - Python
:A Wget-compatible web downloader/crawler.
DirectCanada

DirectCanada is a Canadian computer parts and electronics e-tailer, which shifted to a business-to-business model in the mid 2000s, but then shifted back to selling to ordinary consumers by mid-2006. Although it wasn't advertised as such until April 2017, DirectCanada is a sister company of Netlinked Computer Inc., which runs NCIX.
== Vital signs ==
Endangered by bloodline, as its parent is reported to be in significant financial trouble.
Netlink Computer Inc. filed for bankruptcy in British Columbia courts on December 1st, 2017, under file number 170816.
== See also ==
* NCIX
Discourse/archived

* https://forums.lutris.net/ (, started 2024-07-14)
* https://zola.discourse.group/ (, started 2024-07-15)
* https://forums.swift.org/ (, started 2024-08-10)
* https://forum.hackteria.org/ (, started 2024-09-15)
* https://lookmumnocomputer.discourse.group/ (, started 2024-10-11)
* https://community.avast.com/ (, started 2024-10-12)
* https://discuss.dev.twitch.com/ (, started 2024-10-26)
* https://discuss.opensource.org/ (, started 2024-10-27)
* https://discuss.opensourcedefinition.org/ (, started 2024-10-27)
* https://community.raspberryshake.org/ (, started 2024-10-26)
* https://community.hannity.com/ (, started 2024-11-02)
* https://bbs.boingboing.net/ (, started 2024-11-03)
* https://community.openstreetmap.org/ (, started 2024-11-11)
* https://chinwag.pluralistic.net/ (, started 2024-11-12)
* https://discuss.logseq.com/ (, started 2024-11-18)
* https://discourse.joplinapp.org/ (, started 2024-11-20)
* https://talk.arolsen-archives.org/ (, started 2024-11-21)
* https://talk.lagedernation.org/ (, started 2024-12-01)
* https://forum.dbpedia.org/ (, started 2024-12-13)
* https://community.worldpossible.org/ (, started 2024-12-14)
* https://sendegate.de/ (, started 2024-12-31)
* https://discourse.bits-und-baeume.org/ (, started 2024-12-31)
* https://community.coda.io/ (, started 2025-01-02)
* https://llllllll.co/ (, started 2025-01-05)
* https://coq.discourse.group/ (, started 2025-01-09)
* https://community.openenergymonitor.org/ (, started 2025-01-21)
* https://we.opentech.fund/ (, started 2025-02-18)
Discovery Data

Sometimes when starting a new project, we gather discovery data from discovery scripts.
== Raw Data ==
Raw data contains unprocessed data from discovery scripts.
* https://archive.org/details/archiveteam-github-repository-index-201212
* https://archive.org/details/2013_10_09_bliptv_urls
=== Smaug's Secret Stash ===
Smaug's Secret Stash is data rsync'ed to user:chfoo's host.
* https://archive.org/details/shipwretched-items
* https://archive.org/details/fotodisco-raw-items
* https://archive.org/details/quizilladisco-raw-items
* https://archive.org/details/qwikidisco-raw-items
* https://archive.org/details/twitpicdisco-raw-items
== Item Lists ==
Item lists are prepared lists of items, such as username or hostname, to be fed into the tracker.
* https://archive.org/details/archiveteam-xanga-userlist-20130142
* https://archive.org/details/2013-02-22-posterous-hostname-list
* https://archive.org/details/2013-02-22-posterous-hostname-list-not-posterous
* https://archive.org/details/Posterous.comHostnames
More can be found on ArchiveTeam's GitHub repository. The repositories are usually suffixed with "-items"
== Datasets ==
Datasets are sets of data useful for research.
* https://archive.org/details/friendster-dataset-201107
* https://archive.org/details/friendster-groups-201107
DiscussionApps

DiscussionApps was a discussion platform operated by The Server Company. Anyone (?) could create a forum ("app") which could then contain threaded discussions. It was shut down on 2019-10-31.
DiscussionApps was part of the bigger YourWebApps platform that was initially launched in 1996 under server.com and relaunched under yourwebapps.com in 2008. The platform used to also offer mailing lists, calendars, databases, and an RSS aggregator, all of which were shut down in the years leading up to 2018. The forum service was the last surviving part.
== Shutdown notice ==
In early March 2019, the homepage was replaced with the following message:
We're very sorry that, after 22 years, we'll be shutting down the DiscussionApps on October 31, 2019.
We've been very happy to have provided this service and we wish you luck with your communities.
The page further had a form for entering an email address to receive "all of your maintenance page URLs".
== Automatic deletion ==
Per the error message when trying to access an inexistent "app", forums got deleted from the platform if there had been no activity in 12 weeks. By the time of the shutdown, the vast majority of forums had already disappeared along with all their messages due to this.
== Archival ==
User:JustAnotherArchivist archived what remained of the platform in late October 2019. The data is at .
The outlinks found in the messages during this retrieval were archived with ArchiveBot in and .
Discussion group

User:DiscussionArchiver has created PHP scripts that scrape discussion groups.
==vBulletin==
==phpBB==
*viewforum.php?f=<category_id>
*viewtopic.php?t=<discussion_id>
==myBB==
===Dynamic URLs===
*forumdisplay.php?<category_id>
*showthread.php?tid=<discussion_id>
===Static URLs===
*forum-<category_id>.html
*thread-<discussion_id>.html
==xenForo==
*threads/<discussion_id>/
*forums/<category_id>/
==Hosted discussion group websites==
{| class="wikitable sortable"
|-
! Site
! Status
! Saved?
! Number of Accounts
! Number of Groups
! Number of Discussions
! Number of Messages
|-
| DelphiForums
| Online
| No
| 4,000,000
| > 8,000
| 25,000,000
| 300,000,000
|-
| Facebook Groups
| Online
| No
| 1,000,000,000
| 500,000,000 (2013)
| ?
| ?
|-
| FreeForums.org
| Online
| No
| ? 
| ?
| ?
| ?
|-
| Forumotion
| Online
| No
| ?
| ?
| ?
| ?
|-
| Google Groups
| Online
| No
| ?
| ?
| ?
| ?
|-
| Lefora
| Online
| No
| ?
| ?
| ?
| ?
|-
| Nabble
| Online
| No
| ?
| ?
| ?
| ? 
|-
| Proboards
| Online
| No
| 22,800,000
| 3,000,000
| ? 
| ?
|-
| Yahoo! Groups
| Online
| No
| ?
| ? 
| ?
| ?
|-
| Yuku
| Online
| No
| ?
| ? 
| ?
| ?
|-
| ZetaBoards
| Online
| No
| ?
| ? 
| ?
| ?
|-
}
Disqus

Disqus is a comment hosting service, apparently by far the most popular one, apart from Facebook. They claim hosting 50 million comments per monthhttps://disqus.com/company/, and recent comment IDs in threads suggest that the total number of comments exceeds 4 billion (as of August 2018).
Disqus was founded in 2007 as a startup and was acquired by Zeta Global in 2017https://en.wikipedia.org/wiki/Disqus. (Worth noting, as startups are often subjects to, and acquisitions are often signs of, upcoming closures.)
== Archiving ==
Disqus heavily utilizes JavaScript, so the Wayback Machine doesn't save Disqus comments.
Although Disqus threads can also be read on disqus.com, they should be saved along with the article they belong to. However, 750,000 websites (mainly blogs and news websites) had Disqus already back in 2011.
Even if we find the method to archive Disqus threads, discovering all the websites using it and saving all those articles wouldn't (won't) be a simple task.
A sustainable approach would be continuously achiving major news websites that use Disqus, with a focus on also archiving the corresponding Disqus threads. This is the aim of the recently started News+C project.
== Disqus Channels ==
Disqus Channels is a standalone discussion part of Disqus, i.e. a series of forums that is not attached to any website. Except for the official forum on the Disqus platform itself (), it was shut down on 2019-09-01 due to moderation overhead.
All discoverable channels and their contents (348 channels, 625k discussions) were archived by User:JustAnotherArchivist shortly before the shutdown. This crawl can be found at . Due to Disqus's heavy reliance on JavaScript, playback in the Wayback Machine is unlikely to be successful. The images included in the comments were grabbed separately in ArchiveBot .
== References ==
[]
Category:News
Category:Blogging
Category:Social networks
Distill

Distill.cc was yet another service killed by Yahoo!. Surprised? It closed on March 30, 2014.
== A New Adventure for the Distill Team ==
We are excited to share the news that the Distill team is off to start a new adventure! We are joining Yahoo. Prior to creating Distill, we were part of the original team behind the creation of Tapjoy, a mobile performance-based advertising platform that drove deep engagement and monetization opportunities for mobile app publishers. We’ll be drawing upon our expertise from the Tapjoy days to help build out Yahoo’s mobile advertising solutions.
As of today, we have stopped development of Distill Schedule and Distill Interview. You will still be able to schedule interviews through the end of February, and the Distill platform will remain available through Sunday, March 30, 2014. If you have any questions, concerns, or data requests, please contact us at support@distill.cc, or reach out to your account manager directly.
We want to express our sincere thanks and gratitude to everyone at the awesome companies we have been working with, as well as the candidates who have met their future employers through Distill. It's been a fun ride for us, and we couldn’t have gotten this far without your help. Thank you!!
The Distill Team 
== About us ==
Interview better together, with Distill
With backgrounds at companies like Google, Yahoo!, Amazon, StumbleUpon, and Tapjoy, all of us at Distill experienced the challenges of identifying the best candidates to interview, and eventually to hire. Distill was created out of the best practices we identified when working at hyper-growth firms when hiring was a key part of the company's success.
We found that we could quickly identify great engineering, product, design, and sales candidates when they came on-site through interactive coding challenges, whiteboarding exercises, sales pitches, or case questions. Distill brings this experience to the screening process with our collaborative video interviewing platform. By moving the most predictive aspects of the interview earlier in the screening process, we enable recruiters and hiring managers to identify the right candidates more quickly and effectively, helping companies hire the right talent as efficiently as possible.
Spend less time organizing candidates and more time hiring the right candidate.
Many tools on the market today, such as applicant tracking systems, are built only to manage a candidate pipeline without adding value to the hiring process. We're focused on optimizing the person-to-person interactions between the company and candidate to make the most accurate assessment possible for predicting on-the-job performance. At Distill, we're building new tools and products that help companies hire smarter and hire faster.
We're proud to work with leading institutional investors, notable angels and a team of experienced advisors to improve hiring and recruiting. 
https://www.distill.cc/about
Category:Yahoo!
Distributed Preservation of Service

A Distributed Preservation of Service (DPoS) is an act similar to a Distributed Denial of Service (DDoS) attack, with the difference that the purpose of the latter is rendering a service unavailable, thus causing harm, while the point of DPoS is quite the opposite: to preserve, if not the service, but at least its content, for future presentation, analyzation, or for other purposes.
The term was introduced by ArchiveTeam founder Jason Scott in his 2011 Defcon presentation titled ARCHIVE TEAM: A Distributed Preservation of Service Attack.
In fact, it means plain web archiving, but from several differently geolocated points at the same time, that is what distributed in the phrase means.
ArchiveTeam has set up a distributed archiving toolkit, which consists of
*a tracker,
*staging servers for temporary storage of archived data,
*custom scripts for different projects,
*and optionally a virtual machine appliance called Warrior that makes joining the DPoS operation easier.
ArchiveTeam often uses the phrase warrior project – those are all DPoS's. Sometimes, however, the Warrior is not used, but only the scripts: in those cases we can only say that it's a DPoS project.
Category:ArchiveTeam Glossary
Dmoz

DMOZ, also known as the Open Directory Project, is the largest human-edited directory on the Web. On 2017-02-28 it was announced that DMOZ would be shutting down on 2017-03-14.https://web.archive.org/web/20170228213058/http://www.dmoz.org/https://tech.slashdot.org/story/17/03/05/025208/after-19-years-dmoz-will-close-announces-aol
== References ==
== External links ==
* http://www.dmoz.org/
* Database download: http://www.dmoz.org/rdf.html
Category:Archive Team
Docker Hub

Docker Hub is Docker, Inc.'s public registry for Docker images.
== Deletion of inactive images ==
On 2020-08-24, it was announced that inactive images, defined as ones that haven't been pulled in 6 months, associated with free accounts would be deleted starting on 2020-11-01. According to Docker, Inc., this amounts to 4.5 PB of data.https://web.archive.org/web/20200823013653/https://www.docker.com/pricing/retentionfaq – This information was later removed from the FAQ. On 2020-10-22, it was announced that this deletion would be postponed until mid-2021.
== Sunset of Free Teams ==
On 2023-03-14, Docker, Inc. announced in an email to affected organisations that they would discontinue their Free Teams plan a month later.
Docker is sunsetting Free Team organizations
Free Team organizations are a legacy subscription tier that no longer exists. This tier included many of the same features, rates, and functionality as a paid Docker Team subscription.
After reviewing the list of accounts that are members of legacy Free Team organizations, we’ve identified yours as potentially being one of them.
If you own a legacy Free Team organization, access to paid features — including private repositories — will be suspended on April 14, 2023 (11:59 pm UTC). Upgrade your subscription before April 14, 2023 to continue accessing your organization.
If you don’t upgrade to a paid subscription, Docker will retain your organization data for 30 days, after which it will be subject to deletion. During that time, you will maintain access to any images in your public repositories, though rate limitations will apply. At any point during the 30-day period, you can restore access to your organization account if you upgrade to a paid subscription. Visit our FAQ for more information.
The FAQ instead says that at least private repositories of the organisations will be suspended as of 2023-04-13:
If you currently are accessing a legacy Free Team organization and using private repos, they will be suspended as of April 13, 2023.
Free Team organisations are often used by open-source projects, and while Docker, Inc. continues to offer free hosting to open-source projects upon application, there are severe restrictions on that. Likely, many open-source projects won't bother with it.
On 2023-03-16, Docker, Inc. published a blog post apologising for their grossly misleading announcement. In particular, this post states that public images of affected organisations would not be deleted unless that is done manually by 'the maintainer', without clarifying who the maintainer of a shared account will be after the tier is discontinued.
On 2023-03-24, they announced in another blog post that the plan to sunset Free Teams has been buried:
After listening to feedback and consulting our community, it’s clear that we made the wrong decision in sunsetting our Free Team plan. Last week we felt our communications were terrible but our policy was sound. It’s now clear that both the communications and the policy were wrong, so we’re reversing course and no longer sunsetting the Free Team plan.
== References ==