» Glossary 0-9 » Glossary A-D » Glossary E-J » Glossary K-R » Glossary S-Z » File Extensions » Tools

Nuke Synonyms: nuked Terminology | Dictionary | Explanation A nuke occurs when a release violates the scene rules. There can be various reasons for a nuke. Some examples of this would be a bad crack for a program, a video release that is out of sync or has a bad aspect ratio, or skipping in a mp3 release. Also, if a group publishes a release which already has been released by another releasegroup, it's a dupe (derived from duplicate). When a release is nuked, it means that it is marked as a bad release. Releasegroup try to avoid nukes, since this will give them a bad reputation. All nukes include a reason, which are displayed in the pre channels. Typically a release gets nuked by people who have special access to the prebots that echo and relay information to each other. These people are called nukers. Nukers are designated people who check releases to make sure they are error free and comply with scene rules. Prebot owners and sources close to them may also issue a nuke themselves if they come across a defective release, since there are thousands of releases everyday and it is near impossible to spot and find every defect on the spot. Other sceners may also initiate a nuke request command in a pre channel. Then a nuker will check the release in question. If it's a nuke reason is valid, he will perform the nuke. A release can also be unnuked. It's not a rare thing that a release will be nuked incorrectly. The reason for the nuke may be based on incorrect information. It is also possible that the group fixes the release with a dirfix, nfofix, samplefix, synchfix or a ppf patch. This is only possible in case of minor errors. In case of a big error, a repack or rerip is required. To clear the status of the release in the pre channels and release databases, the release will be unnuked. It may get unnuked by fellow nukers or prebot owners and close sources. Also other sceners can request a nuke with the unnuke request command. Unnukes are also followed by a reason. Local nukes Up till now we've talked about nukes as global nukes. When a release is nuked globally, it's nuked because there is something wrong with the release itself. A release can also be nuked locally, as on a single (top)site. Individual sites will nuke releases which are not allowed to be traded to the site. For example, no cam/ts/screeners, or no foreign movies. So there is nothing wrong with the release itself. Since these releases are nuked locally, they can still be traded on other sites. Nukewars Nuke and unnuke access can be abused by people. Nuke wars ensue when there is a disagreement about a release. In a nuke war, a release will cycle between nuked and unnuked status. There is no person that decides who wins a nuke war, the winner is the person who has the most free time. Some lame groups which have nuke/unnuke access or know someone with access, and will unnuke their own group releases' even though the nuke is valid so their nuke percentage rate does not increase. Nuke wars also stem from bad blood or just plain propaganda. Groups may nuke another group's release and issue a proper. Both of the releases may cycle through nuke/unnuke status; almost always the nuke and unnukes come from the two groups. Since nuke wars create a lot of spam in pre channels, many prebot owners will simply "flag" the release so it can't be un/nuked anymore. Technical information Nuke command usage: Nuke command: !nuke <release> <reason> Unnuke command: !unnuke <release> <reason> Nuke request commands: !nukereq <release> <reason> and !unnukereq <release> <reason> Any specific nuke commands: Dupe: !nuke <release> dupe.GROUP.YYYY-MM-DD Repack: !nuke <release> reason_get.repack Proper: !nuke <release> reason_get.GROUP.proper Minor update: !nuke <release> mu.GROUP.YYYY-MM-DD Common nuke releases (except for ones listed above) » bad.ar (Bad aspect ratio) » oos (Out of sync) » grp.req (Group request) » bad.ivtc (Bad inverse telecine, the process of converting framerates was incorrect) » Interlaced, black lines on movement as the field order is incorrect » Overscan (Bad crop) Nuker guidelines & rules » Do not nuke unless you are 100% sure its a valid nuke » Keep your (un)nuke reasons clean. No personal comments or bad language » Be professional towards responding to "nukewar" nukes » Do not nuke spam/fakes; use !delpre <title> to delete them » Do not distribute people's names etc » Be specific with your (un)nukes » No nuke wars         [ Your advertisement here? ]

© AboutTheScene.com 2007 :: All rights reserved | Site Disclaimer