The nuke is issued by a nuke command in a nuke channel. Titles can only be officially labeled as "nuked" by people who have special access to a listing database, often referred to as "nukers". Drink Or Die created the first web dupe check. It let the user connect to an SQL database, offering greater speed and flexibility over the IRC bots. Katman, a siteop of Quadcon (QC), created a native win95 program named WinDupe. In 1998 a new kind of dupe check appeared. The most popular dupe checks were ran out of #releases and #thescene. Īt the end of the 1990s, the various IRC dupe checks were the simplest to use. It allows couriers to check when a release already exists on a site and the release groups avoid duplicating an earlier release of another group. These dupe check scripts or programs allows users to search warez releases by date or name. It kept a history of releases that were moved offline by storing the DIZ files included in the ZIPs. History ĭupe checkers first showed up on BBSes to help sysops nuke duplicate uploads. The person that uploaded the nuked content to a site will lose credits. A nuke merely serves as a cautionary flag to potential users. Ĭontrary to what the term implies, a nuke does not actually destroy offending content or prevent anyone from downloading it. When a scene release is "nuked", a message is attached to its listing informing other sceners of its "nuked" status, as well as the specific nature of the problem. Duplicates and stolen releases from other pirates that do not attribute the original pirates will also be nuked. In the warez scene, to nuke is to label content as "bad", for reasons which might include unusable software, bad audiovisual quality, virus-infected content, deceptively labeled (fake) content or not following the rules. For "topsite" nukes, see Topsite (warez) § Credit system. This article is about nukes for individual warez releases.
0 kommentar(er)
