Nuke (warez)#Pre database

Dupe checkers first showed up on BBSes to help sysops nuke duplicate uploads. It kept a history of releases that were moved offline by storing the DIZ files included in the ZIPs. These dupe check scripts or programs allows users to search warez releases by date or name. 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.{{cite journal |url=http://www.scenelink.org/features/issue/5/dupe.html |author=MeAD |date=February 1998 |title=Dupe checks: an introduction |journal=Scenelink |issue=5 |archive-url=https://web.archive.org/web/19980626140716/http://www.scenelink.org/features/issue/5/dupe.html |archive-date=1998-06-26 |url-status=dead}}

At the end of the 1990s, the various IRC dupe checks were the simplest to use. The most popular dupe checks were ran out of #releases and #thescene. In 1998 a new kind of dupe check appeared. Katman, a siteop of Quadcon (QC), created a native win95 program named [http://rescene.wikidot.com/windupe WinDupe]. It let the user connect to an SQL database, offering greater speed and flexibility over the IRC bots. Drink Or Die created the first web dupe check.

Titles can only be officially labeled as "nuked" by people who have special access to a listing database, often referred to as "nukers". The nuke is issued by a nuke command in a nuke channel.{{cite web|url=http://scenerules.irc.gs/rules.html |title=Basic nuke channel rules |work=SceneRules |archive-url=https://web.archive.org/web/20211103164746/http://scenerules.irc.gs/rules.html |archive-date=2021-11-03 |url-status=live }} For example:

!nuke release reason [source] (nukes a release)

!unnuke release reason [source] (unnukes a release)

!renuke release reason [source] (renukes a release)

!modnuke release reason [source] (modifies a nuke reason)

!snuke release reason [source] (a silent nuke: not announced in announce channels)

!oldnuke release reason [source] (for old releases, also a silent nuke)

Erroneous nukes are usually "un-nuked" easily, by the same people who have access to issue nukes, that nukes and unnukes happen on IRC. These nuke networks have their own guidelines on how to nuke a release.

{{cite web

|url=http://justsomerules.synthasite.com/onenet-rules.php

|title=oneNET nuke net rules

|date=2008-04-18

|archive-url=https://web.archive.org/web/20100805124829/http://justsomerules.synthasite.com/onenet-rules.php

|archive-date=2010-08-05

|url-status=live

}}

In 2008, twelve of those nuke networks created a coalition to work together "to ensure nukers bias, nukewars and many other problems that plague the nuke scene become a thing of the past."{{cite web|url=https://scenerules.org/t.html?id=2008_NC.nfo|title=The.2008.Nuke.Ruleset-NukeCouncil|date=2008-11-08|work=SceneRules}}

{{details|Topsite (warez)#Credit system}}

Local nukes or site nukes can be issued by a topsite administrator and are only applicable to that site. Each individual site has rules for which kind of releases that are allowed. e.g. no VCD releases. Hence a locally nuked release can still be valid.

The situation where a release is nuked or unnuked more than four times is called a nukewar.

Example

{{cite web|url=http://www.rlslog.net/hellgate-london-vitality-vs-flt/ |title=Hellgate London: nukewar between ViTALiTY and FLT |author=Martin |date=2007-11-01 |work=RlsLog.net |archive-url=https://web.archive.org/web/20110721075153/http://www.rlslog.net/hellgate-london-vitality-vs-flt/ |archive-date=2011-07-21 |url-status=live

}} of a nukewar. The first two columns represent the time when the release was pred or when a nuke was issued. The next column is the category of the release.{{cite web|url=http://doopes.com/index.php?cat=33792&lang=0&num=2&mode=0&from=&to=&exc=&inc=Crossing.Jordan.S06E07&opt=0 |title=Crossing Jordan: nukewar between NoTV and XOR |work=Doopes.com |archive-url=https://web.archive.org/web/20110710144326/http://doopes.com/index.php?cat=33792&lang=0&num=2&mode=0&from=&to=&exc=&inc=Crossing.Jordan.S06E07&opt=0 |archive-date=2011-07-10 |url-status=dead}} In this example two releases were released at almost the same time.

2007-03-08 04:15:26 TV Crossing.Jordan.S06E07.HDTV.XviD-NoTV

2007-03-08 04:15:32 TV Crossing.Jordan.S06E07.HDTV.XviD-XOR

2007-03-08 04:16:16 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV NUKED dupe.XOR.same.day

2007-03-08 04:20:21 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR NUKED lost.race.to.NoTV

2007-03-08 04:21:59 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV NUKED dupe.XOR.03-07-2007

2007-03-08 04:22:46 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV UNNUKE fix

2007-03-08 04:23:12 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV NUKED dupe.XOR.2007-03-07

2007-03-08 04:23:46 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV UNNUKE NoTV.pred.first

2007-03-08 04:24:47 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR NUKED dupe.NoTV.2007-03-08

2007-03-08 04:38:41 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR UNNUKE is.fine

2007-03-08 04:39:23 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV NUKED dupe.XOR.2007-03-08

2007-03-08 05:18:23 NUKES Crossing.Jordan.S06E07.HDTV.XviD-NoTV UNNUKE won.race

2007-03-08 05:18:50 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR NUKED dupe.NoTV.2007-08-03

2007-03-08 05:20:22 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR UNNUKE fixing

2007-03-08 05:24:03 NUKES Crossing.Jordan.S06E07.HDTV.XviD-XOR UNNUKE fix_won.race.against.NoTV

Another source shows different timestamps.{{cite web|url=http://orlydb.com/?q=Crossing.Jordan.S06E07|title=OrlyDB.com search result|work=OrlyDB.com|archive-url=https://archive.today/20110715014921/http://orlydb.com/?q=Crossing.Jordan.S06E07|archive-date=2011-07-15|url-status=dead}} Site name is based on the O RLY? Internet phenomenon.

The clock of a computer is not always accurate. This and the difference in time zone partially explain the time difference. This shows why this nukewar was started.

2007-03-08 03:14:07 TV-XVID Crossing.Jordan.S06E07.HDTV.XviD-XOR

2007-03-08 03:14:14 TV-XVID Crossing.Jordan.S06E07.HDTV.XviD-NoTV

ZoNeNET, EthNet and oneNET confirmed the precedent to leave both releases unnuked when groups pre within the same second. This did not prevent a small nukewar between the LocalNet and SanctityDenied networks in 2020.{{cite web|url=https://twitter.com/Xylit0l/status/1272722959363342336|title=Barn.Finders-CODEX nukewar|quote=not so long ago, also nukewarz is still a thing (:|date=2020-06-16|archive-url=https://web.archive.org/web/20200616024943/https://twitter.com/Xylit0l/status/1272722959363342336|archive-date=2020-06-16|url-status=live|access-date=2022-08-06}}

Barn_Finders-HOODLUM, nukes on Barn.Finders-CODEX

2020-06-15 17:15:00 SanctityDenied/dupe.HOODLUM.2020-06-15

2020-06-15 17:44:00 LocalNet/not.dupe_pred.within.1.second_precedent.is.to.leave.both.unnuked

2020-06-15 18:33:00 SanctityDenied/no.such.rule.in.iso.rules_dupe.HOODLUM.2020-06-15

2020-06-15 18:39:00 LocalNet/pred.with.1.second.of.each.other.precedent.is.to.leave.both.unnuked_precedent.applies.to.all.sections.and.is.not.a.rule_apply.common.sense

The.Game.S06E18.HDTV.x264-ASAP

NUKE dupe.EVOLVE.2013-08-21/ZoNeNET

UNNUKE fine_pred.same.second.so.both.rls.are.fine/ZoNeNET

The.Walking.Dead.S04E12.PROPER.HDTV.x264-2HD

NUKE dupe.KILLERS.2014-03-03/ZoNeNET

UNNUKE fine_both.pred.within.one.second.of.each.other_basis.has.been.to.leave.both.alone_

see.zonenets.unnuke.on.The.Game.S06E18.HDTV.x264-ASAP/EthNet

NUKE dupe.KILLERS.2014-03-03_KILLERS.won.the.proper/ZoNeNET

UNNUKE fine_groups.pred.within.the.same.second_precedent.is.to.leave.both.unnuked/oneNET

Another example is the nukewar about the TDRS2K10 ruleset.{{cite web|url=http://pre.zerosec.ws/?cmd=search&pre=THE.2010.DVDR.RELEASING.STANDARDS-TDRS2K10 |archive-url=https://web.archive.org/web/20110825014520/http://pre.zerosec.ws/?cmd=search&pre=THE.2010.DVDR.RELEASING.STANDARDS-TDRS2K10 |url-status=dead |archive-date=2011-08-25 |title=THE.2010.DVDR.RELEASING.STANDARDS-TDRS2K10 nukes}}

{{cite web|url=http://filenetworks.blogspot.com/2009/11/scene-dvdr-releasing-standards-2010.html |title=Scene DVDR Releasing Standards 2010 (TDRS2K10) |work=FileNetworks

|archive-url=https://web.archive.org/web/20110708035553/http://filenetworks.blogspot.com/2009/11/scene-dvdr-releasing-standards-2010.html |archive-date=2011-07-08 |url-status=live}} The name between the square brackets is the nuke network where the nuke originates from. Each of those networks in this example was also a council member network.

Nuked on 2009-11-14 15:15:09 [LocalNet]

crap_signing.grps.are.crap_for.small.changes.create.a.adendum

Unnuked on 2009-11-14 15:20:56 [oneNET]

this.ruleset.is.real.and.legit.leave.it.alone

Nuked on 2009-11-14 20:51:10 [Nuclear]

signing.grps.are.crap_for.small.changes.create.an.adendum.or.rebuttal.to.tdrs2k9_invalid.ruleset

Unnuked on 2009-11-14 20:52:23 [LocalNet]

invalid.nuke_nukenets.do.not.have.the.authority.to.invalidate.rulesets_such.things.are.left.to.section.groups.and.leaders

Nuked on 2009-11-14 20:52:25 [Nuclear]

signing.grps.are.crap_for.small.changes.create.an.adendum.or.rebuttal.to.tdrs2k9_invalid.ruleset

Unnuked on 2009-11-14 20:52:26 [LocalNet]

invalid.nuke_nukenets.do.not.have.the.authority.to.invalidate.rulesets_such.things.are.left.to.section.groups.and.leaders

Nuked on 2009-11-14 21:23:31 [Nuclear]

no.leading.groups.signed_valid.nuke_2k5.was.rewritten.with.2k9.inserts_release.a.rebuttal.or.addendum

Unnuked on 2009-11-14 21:55:04 [LocalNet]

invalid.nuke_nukenets.do.not.have.the.authority.to.invalidate.rulesets_such.things.are.left.to.section.groups.and.leaders_it.is.not.your.duty.to.decide.which.groups.are.good.enough

Examples of content that could be "nuked" include non-working software, non-working cracks, videos with out-of-sync audio, watermarked videos, or music recordings with excessive "skips". The reason for a nuke is based on violations of the standards that must be followed.

Spam entries in release databases are deleted but marked as soft deleted, with the status delpre, to ensure they no longer appear in regular searches. There are several reasons for this, including instances when the release does not actually exist, when it does not originate from the scene itself (peer-to-peer), or when the name of a legitimate release becomes distorted during transmission (cut echo). One example is when a fake name is shared to monitor communication between bots and networks, but the record is later deleted with leak.test as the reason.{{cite web |url=https://predb.pw/nuke.php?status=4 |title=Delete releases |website=preDB.pw |archive-url=https://web.archive.org/web/20220219205501/https://predb.pw/nuke.php?status=4 |archive-date=2022-02-19 |url-status=live}}

When a release is mistakenly deleted, it is assigned the status undelpre. This can occur when releases that appear suspicious or questionable are removed. Here are various examples:{{cite web |url=https://predb.pw/nuke.php?status=7 |title=Undelete releases |website=preDB.pw |archive-url=https://web.archive.org/web/20220219205817/https://predb.pw/nuke.php?status=7 |archive-date=2022-02-19 |url-status=live}}

VA-H0rd3z_Ov_Thee_El33t-2006-SnS

EthNet: real

From.The.Earth.To.The.Moon.1998.INTERNAL.Part.1.WS.DVDRip.XviD.-FRAGMENT

EthNet: real

INCOMPLETE-I-N-C_Am_Mic_(JMC_Qualifikation_57)-WEB-DE-2016-VOLDiES_iNT

EthNet: crap.maybe_real.nonetheless

Sinik_Cheb_Billal_And_Big_Ali-Bienvenue_Chez_Les_Bylkas-PROPER-x264-FR-2008-NaWaK.mkv

EthNet: it.was.pred.this.way_seriously

TCF-415C47197F78E811FEEB7862288306ECFD4EC3DED8B-WEB-2014-BCC

EthNet: not.spam_real.release

Love.Thy.Neighbor.2013.S03E06.HDTV.x264-CRiMSO

EthNet: not.a.cut.echo_sitepred.BEFORE.CRiMSON.rls.and.traded.too sitepred.and.raced.before.CRiMSON

A pre network (aka a Nukenet) is a collection of databases which share information about releases among the members of the network. There have been at least 30 different pre networks.{{cite web |title=Top nuke networks |website=preDB.pw |url=https://predb.pw/stats-nuke.php |archive-url=https://web.archive.org/web/20230319151458/https://predb.pw/stats-nuke.php |archive-date=2023-03-19|url-status=live}}{{cite web|url=http://scenegrouplist.com/lists_nukenets.php |title=Incomplete list of Nukenets |archive-url=https://web.archive.org/web/20100919153652/http://scenegrouplist.com/lists_nukenets.php |archive-date=2010-09-19 |url-status=dead}}{{cite web|url=http://predb.in/database.txt|title=Network statistics|date=2011-09-18|work=PreDB.in|archive-url=https://web.archive.org/web/20121105041227/http://predb.in/database.txt|archive-date=2012-11-05|url-status=dead}} Peers can be linked to more than one network. Linking to other network provides information which isn't available on peers local pre network. Such information can be .sfv, .m3u, .jpg, .diz or .nfo files.{{cite web|url=http://layer13.it.cx/?p=home|title=DB stats|work=Layer13.it.cx|archive-url=https://web.archive.org/web/20160306182243/https://layer13.net/?p=home|archive-date=2016-03-06|url-status=dead}}

Each release that gets released will result as a record in a pre-database or dupe check.

{{cite web|url=http://torrentfreak.com/27-years-of-warez-scene-release-info-leaked-in-giant-database/ |title=27 Years of Warez Scene Release Info Leaked in Giant Database

|date=2007-08-11 |author=enigmax |archive-date=2010-02-03 |url-status=live

|archive-url=https://web.archive.org/web/20100203004715/http://torrentfreak.com/27-years-of-warez-scene-release-info-leaked-in-giant-database/}}

This record will at least contain the time the release was released and the release name (the name of the folder that contains the files of the release).{{cite web |url=http://www.aboutthescene.com/thescene/system.html |archive-url=https://web.archive.org/web/20070122030345/http://www.aboutthescene.com/thescene/system.html |archive-date=2007-01-22 |title=The scene / topsite system}}

The size and nature of the release are often provided too.{{cite web |author=Ghandy |url=http://www.gulli.com/news/1830-nfokingzorg-admins-im-interview-2009-05-15 |title=NfoKingz.org: Admins im Interview |trans-title=NfoKingz.org: Admins interview |language=de |work=Gulli.com |date=2009-05-15 |archive-url=https://archive.today/20130125180214/http://www.gulli.com/news/1830-nfokingzorg-admins-im-interview-2009-05-15 |archive-date=2013-01-25 |url-status=dead}}

Nukes are linked with their release in these databases when a nuke is issued. To check if a release is nuked, a scener uses an IRC channel to query the database by typing commands. These IRC channels are called pre channels and are often not accessible for the general public.

{{cite web|url=http://filenetworks.blogspot.com/2010/02/trac3me-public-predb-scene-release.html |title=TRAC3.ME – Public PreDB, Scene Release Index and Torrent Tracer |date=2010-02-25 |quote=Trace.M3 maintains a pre database that indexes hundreds of scene and p2p releases daily. However, T.ME's PreDB differs from those run by pure sceners – first of all it's publicly accessibly by anyone. |archive-url=https://web.archive.org/web/20110708035652/http://filenetworks.blogspot.com/2010/02/trac3me-public-predb-scene-release.html |archive-date=2011-07-08 |url-status=live}}

The database is updated automatically through spidering topsites or by catching pre-release announcements from site channels.

The purpose of these different worldwide and mirrored pre databases is to check for fakes and that for example a music album or movie isn't pred more than once and thus reducing traffic.

There are now several public websites and IRC channels that list the contents of pre-databases. Most of them are regularly updated and show nuke reasons next to their release. They can be regularly down, very slow when searching or disappeared entirely.{{cite web |url=https://tarnkappe.info/nfo-sites-sterben-langsam-vor-sich-hin/ |title=NFO Sites sterben langsam vor sich hin |language=de |trans-title=NFO sites are slowly dying out in front of us |date=2015-07-05 |first=Lars |last=Sobiraj |website=Tarnkappe |url-status=live |archive-url=https://web.archive.org/web/20150906192507/https://tarnkappe.info/nfo-sites-sterben-langsam-vor-sich-hin/ |archive-date=2015-09-06}} The server time is shown on some of them. According to TorrentFreak these websites are "simple archives of information that cannot be claimed by copyright holders, but anti-piracy companies apparently cannot tell the difference between reporting news and offering pirate releases for download."{{cite web |first=Andy (enigmax)|last=Maxwell |title=Reporting When Pirate Releases Hit The Internet is Apparently Illegal Now |date=2019-01-01 |website=TorrentFreak |url=https://torrentfreak.com/reporting-when-pirate-releases-hit-the-internet-is-apparently-illegal-now-190101/ |archive-date=2019-01-01 |archive-url=https://web.archive.org/web/20190101221107/https://torrentfreak.com/reporting-when-pirate-releases-hit-the-internet-is-apparently-illegal-now-190101/ |url-status=live}}

• https://predb.me/ - 10.4 million releases in the database (September 2023).
• https://predb.net/ - 11.8 million releases in the database (September 2023).
• https://predb.org/
• https://pre.corrupt-net.org/{{cite web |first=Andy (enigmax)|last=Maxwell |title=Which Torrent Sites Get Releases The Fastest (and why it's not a secret) |url=http://torrentfreak.com/which-torrent-sites-get-releases-the-fastest-and-why-its-not-a-secret-101106/ |work=TorrentFreak |access-date=2010-11-06 |url-status=live |archive-url=https://web.archive.org/web/20110108021539/http://torrentfreak.com/which-torrent-sites-get-releases-the-fastest-and-why-its-not-a-secret-101106/ |archive-date=2011-01-08}}{{cite web|last=Whitson|first=Gordon|title=Corrupt-Net Shows You Which Torrent Trackers Get New Releases First |url=http://lifehacker.com/5683783/corrupt+net-shows-you-which-torrent-trackers-get-new-releases-first |work=LifeHacker |date=7 November 2010 |access-date=2010-11-07 |archive-url=https://web.archive.org/web/20101124191913/http://lifehacker.com/5683783/corrupt+net-shows-you-which-torrent-trackers-get-new-releases-first |archive-date=2010-11-24 |url-status=live}} - 7.5 million releases
• https://predb.pw
• https://predb.club - 500,000 releases (November 2023).

A pre channel is an IRC channel in which a prebot announces new warez (pre) releases in real time. Pre channels are generally provided as a convenience to members of the scene, often in conjunction with a topsite. Pre channels are typically private.

Advantages:

• Members of a pre channel are notified about new warez releases as they are released. This is of particular benefit to couriers and release groups.
• Pre channels commonly announce when a release is nuked or un-nuked.
• Pre channels provide a search facility that allows users to find out if a release exists, when it was released, and if it has been nuked. This function may also be used by release groups to avoid dupes (duplicates).
• Pre channels are also used for topsites to measure how fast they received the release, otherwise known as the pretime.

Disadvantages:

• Pre channels are often supplied with events from other pre channels, so spam may spread quickly. Many prebots employ elaborate filters to ensure only valid release events are announced.{{cite web|url=http://torrentfreak.com/shining-light-on-the-warez-darknet-a-scene-insider-speaks/ |title=TorrentFreak - Interview with a scene insider |date=2007-05-18 |author=enigmax |publisher=TorrentFreak |archive-url=https://web.archive.org/web/20100707101123/http://torrentfreak.com/shining-light-on-the-warez-darknet-a-scene-insider-speaks/ |archive-date=2010-07-07 |url-status=live}} Scener mentions bullshit nukes.
• It just gives you the release name and no quality details, plot/features or links to downloads.{{cite web |url=http://www.rlslog.net/public-irc-pre-channel-and-how-to-use-it/ |title=Public IRC PRE Channel and How to use it |author=Martin |work=RlsLog.net |date=2008-08-25 |archive-url=https://web.archive.org/web/20100618104532/http://www.rlslog.net/public-irc-pre-channel-and-how-to-use-it/ |archive-date=2010-06-18 |url-status=live}}

• IRC Server: irc.zenet.org port: +6697 channel: #pre
• http://filenetworks.blogspot.com/2010/09/corrupt-net-new-p2p-friendly-irc.html
• http://filenetworks.blogspot.com/2010/12/list-of-public-pre-trace-services-to.html
• https://opentrackers.org/links/warez-scene/#rlsdb
• LilleSky.org: irc.lillesky.org:6667 (+7000 ssl)

A prebot is commonly known as an automated script in IRC channels that announces new releases and can let users query its database to view past warez release dates and nukes, among other things.{{Cite web|url=https://github.com/haaja/prebot|title = Prebot for Irssi| website=GitHub |date = 21 August 2021}} Another kind of prebot was adopted in 2000 due to the increased competition among release groups. This prebot automatically distributed new releases to affiliated topsites of a group to release faster and more efficiently. This solved geographical and time zone related issues.

• Standard (warez)
• Topsite (warez)
• Warez scene
• Warez group

{{reflist|colwidth=30em|refs=

{{Cite journal | last1 = Goode | first1 = S. | title = Exploring the supply of pirate software for mobile devices: An analysis of software types and piracy groups | doi = 10.1108/09685221011079171 | journal = Information Management & Computer Security | volume = 18 | issue = 4 | pages = 204 | year = 2010 }} "These corrections, called "nukes", can occur when a release is broken, falsified, or incorrectly named, or if another group has already released that same piece of software."

{{Cite journal | last1 = Basamanowicz | first1 = J. | last2 = Bouchard | first2 = M. | doi = 10.2202/1944-2866.1125 | title = Overcoming the Warez Paradox: Online Piracy Groups and Situational Crime Prevention | journal = Policy & Internet | volume = 3 | issue = 2 | pages = 79 | year = 2011 }} "When a group releases content which is defective, improperly cracked, or which does not conform to scene specifications, it will be deleted from the scene in a process referred to as being "nuked" (TGSC Editor 2010). This entails removal from one or all sites in the scene: site operators will have their time and space wasted, couriers who uploaded the content will lose site credits and valuable time, and end users who downloaded the content will have wasted their download credits and time on useless content. Groups that release content that is continually nuked may be banned from uploading content to particular sites. To avoid this, groups test their releases rigorously to ensure quality (McCandless 1997)."

{{cite journal |title=Explaining the rise and fall of the Warez MP3 scene: An empirical account from the inside |first1=Ard |last1=Huizing |first2=Jan A. |last2=van der Wal |url=http://firstmonday.org/ojs/index.php/fm/article/view/5546/4125 |journal=First Monday |volume=19 |issue=10 |date=2014-10-06 |doi=10.5210/fm.v19i10.5546 |issn=1396-0466 |doi-access= free}}

{{cite book |last1=Craig |first1=Paul |last2=Ron |first2=Mark |editor1-first=Mark |editor1-last=Burnett |others=Publisher: Andrew Williams, Page Layout and Art: Patricia Lupien, Acquisitions Editor: Jaime Quigley, Copy Editor: Judy Eby, Technical Editor: Mark Burnett, Indexer: Nara Wood, Cover Designer: Michael Kavish |title=Software Piracy Exposed - Secrets from the Dark Side Revealed |date=April 2005 |publisher=Syngress Publishing |location=United States of America |isbn=1-932266-98-4 |doi=10.1016/B978-193226698-6/50030-1 |pages=[https://archive.org/details/softwarepiracyex0000crai/page/96 96–102] |chapter=Chapter 5: The Release |quote=Ironically, pirates who steal from other pirates will have their own releases nuked. Honor among thieves; pirates do not steal from other pirates.|chapter-url=https://archive.org/details/softwarepiracyex0000crai/page/96 }}

}}

• [https://web.archive.org/web/20120930163430/http://www.rlslog.net/nukes/ RLSLOG Nuke Dictionary] - List of common scene nukes for Xvid movies.
• [http://nuke.sipsik.net/ NUKE pHun] - Collection of funny or weird nukes.
• [http://scenelingo.wordpress.com/2008/07/16/what-does-nuked-mean/ Scene Lingo] - What does "NUKED" mean?
• [http://rescene.wikidot.com/scene-databases Public predb dumps] - SQL database backups.

{{DEFAULTSORT:Nuke (Warez)}}

Category:Warez