About the scene:
The scene system

The scene / topsite system

In the scene hierarchy we already explained what a topsite is. Here we'll provide some more detailed information about topsites and their system, and the scene system. Security ofcourse is a very important issue. Topsites are very private. A typical topsite configuration will only allow users to login from a certain ident and host (or ip range), with SSL encryption on all FTP sessions. FTP bouncers are commonly used to hide the topsite's real IP address, and to share network load. Most users will connect through proxy's. That way the sites won't see their real ip-addresses.

All site members are present in the site's irc channel. These channels are mostly located on private or very secure irc-servers, and you'll need to connect via SSL. Apart from SSL there are more security measures. You cannot just join the channel, you have to invite yourself, by using a command line when you are connected to the site. That way people who are not a member of the site, will not be able to join since it's secured with invite-only or with a channel key (password). Second, the channels are often protected with FiSH. FiSH is a irc addon which encrypts the messages in a channel. That way people who don't have the proper fish key, won't be able to read the messages. In that irc channel, the members and site ops can talk to eachother. Also there is a site eggdrop bot present, which will make an annoucements when a releasegroup publishes a new release on the site, or announces when a members starts to upload a release. Also most sites will have an announce channel. This channel automatically displays the lastest releases just after they're pre'd. More about this below.

Credit system
The site works with a credit system. Site-ops and commonly affiliated are exempt from this system, they have a free leech account. This credit system works according to a ratio. Most common is 3:1, this means when you upload 3 GB, you can download (or fxp) 9 GB. When a member doesn't pass the minimum monthly required amount of upload, he'll automatically be deleted. Credits can be lost by uploading a bad release which gets nuked. Nuke multiplier affects the amount of lost credits.

There are basically three ranks in sitetrading: siteops, affiliates and racers. Siteops (Site-Operators) are the administrators. There are usually between two and five siteops per site. One is often the supplier of the site, another the person who found the supplier and guided them through the installation of the FTPD. The other will be friends and
people involved in the scene. One or more of the siteops will be the nuker. It is his job to nuke any releases that are old or fake. Affiliates are the releasegroups who post their releases there right after they are finished. Each affiliate has access to a private, hidden directory on the topsite. This directory is used for uploading new releases before they are made available to other users.When a new release has finished uploading on each of the group's sites, a command is executed to simultaneously copy it into a directory accessible by other users, and trigger an announcement in the topsite irc channel. This command is called the PRE-command. "To pre" refers to executing this command. Pre-releases may be also relayed to external pre-announce channels to inform other couriers/sitemembers/users from fxp-boards that a new release is available for racing.

The warez scene relies on strict release standards, or rules, which are written and signed by various warez groups.

Release database
DatabaseWhen a group pre's a release, the release will automatically be registered in the pre-database. This is huge database which contains all the releases ever release into the scene. This release databases records release names and their release date & time, although fields vary from database to database. Examples of other common fields include genres (for mp3 releases), sections, and nuke details. Release databases are maintained to provide release groups with a service for checking existing release titles, to avoid a dupe (duplicate). Also users are able to check whether or not, for example, a movie was already released, the releasedate, the status (nuked or not) and more. Release databases are updated by automatic processes that either recurse selected topsites searching for new releases (spidering), or catch pre-release announcements from site channels.

If a group publishes a release which already has been released by another releasegroup, it's a dupe (duplicate). Then the release will be nuked. This means that it's marked as a bad release. Releasegroup try to avoid nukes, since this will give them a bad reputation. Except for dupe, releases can be nuked for other reasons too. First of all, there are 2 types of nuke:
- Global Nuke
Nuked because of the release itself. It is nuked because something is wrong with the release, for example: sound errors, dupe, freezing video, bad rip, etc. If a group realise there is something wrong, they can request a nuke. Common nuke releases:
» Dupe
» Bad aspect ratio
» Bad inverse telecine, the process of converting framerates was incorrect
» Interlaced, black lines on movement as the field order is incorrect
- Local Nuke
Nuked because of the environement. Individual sites will nuke for breaking their rules, for example: no telesyncs, no dvd's subbed in languages other then english and dutch, etc. So there is nothing wrong with the release. Because of these releases are nuked locally, they can still be traded on other sites.