The Golden Rules on RED are as follows:
- Do not create more than one account.
Users are allowed one account per lifetime. Do not create additional accounts under any circumstance. If your account is disabled, contact staff in #red-disabled on IRC.
- Do not trade, sell, give away, or offer accounts.
If you no longer wish to use your account, send a Staff PM and request that your account be disabled. Note, we do not delete accounts.
- Do not share accounts.
Accounts are for personal use only. Granting access to your account in any way (e.g., shared login details, external programs) is prohibited. Invite friends and family if they wish to use the site.
- Do not invite bad users.
You are responsible for your invitees. You will not be punished if your invitees fail to maintain required share ratios, but invitees who break golden rules or invite rules will place your invite privileges and account at risk.
- Do not trade, sell, publicly give away, or publicly offer invites.
Only invite people you know and trust. Staff and approved users may offer invites on other private trackers in designated, user class-restricted invite forums. Do not offer invites on public websites or any private sites that exist solely for the purpose of invite giveaways, trading, and/or selling. Do not offer invites on IRC channels or other social chat clients. Even if you offer the invite in a personal message it is still considered a giveaway and against the rules. Responding to public invite requests is prohibited. See this wiki article for more information about inviting users.
- Do not request invites or accounts.
Requesting invites to—or accounts on—Redacted or other trackers is prohibited. Invites may be offered, but not requested, in the site's Invites forum (restricted to the Power User class and above). You may request invites by messaging users only when they have offered them in the Invites Forum. Unsolicited invite requests, even by private message, are prohibited.
- Do not engage in ratio manipulation.
Transferring buffer—or increasing your buffer—through unintended uses of the BitTorrent protocol or site features (e.g., request abuse) constitutes ratio manipulation. When in doubt, send a Staff PM asking for more information.
- Do not report incorrect data to the tracker (i.e., cheating).
Reporting incorrect data to the tracker constitutes cheating, whether it is accomplished through the use of a modified "cheat client" or through manipulation of an approved client.
- Do not use unapproved clients.
Your client must be found on the Client Whitelist. You must not use clients that have been modified in any way. Developers interested in testing unstable clients must first receive staff approval.
- Do not modify Redacted .torrent files.
Embedding non-Redacted announce URLs in Redacted .torrents is prohibited. Doing so causes false data to be reported and will be interpreted as cheating. This applies to standalone .torrent files and .torrent files that have been loaded into a client.
- Do not share .torrent files or your passkey.
Embedded in each Redacted .torrent file is an announce URL containing your personal passkey. Passkeys enable users to report stats to the tracker.
- Do not blackmail, threaten, or expose fellow users.
Exposing or threatening to expose private information about users for any reason is prohibited. Private information includes but is not limited to personally identifying information (e.g., names, records, biographical details, photos). Information that hasn't been openly volunteered by a user should not be discussed or shared without permission. This includes private information collected via investigations into openly volunteered information (e.g., Google search results).
- Do not scam or defraud.
Scams (e.g., phishing) of any kind are prohibited.
- Do not disrespect staff decisions.
Disagreements must be discussed privately with the deciding moderator. If the moderator has retired or is unavailable, you may send a Staff PM. Do not contact multiple moderators hoping to find one amenable to your cause; however, you may contact a site administrator if you require a second opinion. Options for contacting staff include private message, Staff PM, and #red-disabled on IRC.
- Do not impersonate staff.
Impersonating staff or official service accounts (e.g., Drone) on-site, off-site, or on IRC is prohibited. This includes impersonating staff of other trackers. Deceptively misrepresenting staff decisions is also prohibited.
- Do not backseat moderate.
"Backseat moderation" occurs when users police other users. Confronting, provoking, or chastising users suspected of violating rules—or users suspected of submitting reports—is prohibited. Submit a report if you see a rule violation.
- Do not request special events.
Special events (e.g., freeleech, neutral leech, picks) are launched at the discretion of the staff. They do not adhere to a fixed schedule, and may not be requested by users.
- Do not harvest user-identifying information.
Using Redacted's services to harvest user-identifying information of any kind (e.g., IP addresses, personal links) through the use of scripts, exploits, or other techniques is prohibited.
- Do not use Redacted's services (including the tracker, website, and IRC network) for commercial gain.
Commercializing services provided by or code maintained by Redacted (e.g., Gazelle, Ocelot) is prohibited. Commercializing content provided by Redacted users via the aforementioned services (e.g., user torrent data) is prohibited. Referral schemes, financial solicitations, and money offers are also prohibited.
- Do not browse Redacted using public proxies, Tor, or free VPN services.
Do not browse the site using free proxy or VPN services. Browsing or torrenting through Tor is also forbidden. You may browse the site through paid-for VPN services, private and shared seedboxes, and private servers and proxies. Shared VPNs or VPNs with dynamic IPs need to be approved by staff before use. When in doubt, send a Staff PM seeking approval of your VPN. See our Proxy/VPN Tips and Multiple IPs articles for more information.
- Do not abuse automated site access.
All automated site access must be done through the API. API use is limited to 5 requests within any 10-second window. Scripts and other automated processes must not scrape the site's HTML pages.
- Do not autosnatch freeleech torrents.
The automatic snatching of freeleech torrents using any method involving little or no user-input (e.g., API-based scripts, log or site scraping, etc.) is prohibited. See Redacted's Freeleech Autosnatching Policy article for more information.
- Do not seek or exploit live bugs for any reason.
Seeking or exploiting bugs in the live site (as opposed to a local development environment) is prohibited. If you discover a critical bug or security vulnerability, immediately report it in accordance with Redacted's Responsible Disclosure Policy. Non-critical bugs can be reported in the Bugs Forum.
- Do not publish exploits.
The publication, organization, dissemination, sharing, technical discussion, or technical facilitation of exploits is prohibited at staff discretion. Exploits are defined as unanticipated or unaccepted uses of internal, external, non-profit, or for-profit services. See Redacted's Exploit Policy article for more information. Exploits are subject to reclassification at any time.
A dupe is a torrent that is a duplicate of another torrent that already exists on the site. RED allows many different pressings of the same CD to coexist, as long the the CDs have different content.
For example, International Versions (especially Japanese releases) often have bonus tracks that are not present in the original release or the US release. Uploading a release with bonus tracks when the original release has already been uploaded is not considered a dupe because there is different content on both CDs.
- Torrents that have the same bitrates, formats, and comparable or identical sampling rates for the same music release are duplicates. If a torrent is already present on the site in the format and bitrate you wanted to upload, you are not allowed to upload it.
- Scene and non-scene torrents for the same release, in the same bitrate and format, are dupes.
- Rip log information (table of contents, peak levels, and pre-gaps), tracklist, and running order determine distinct editions, not catalog information. Merely having different catalog numbers or CD packaging is not enough to justify a new, distinct edition, though differences in year and label (imprint) do determine distinct releases.
- Torrents that have been inactive (not seeded) for two weeks may be trumped by the identical torrent (reseeded) or by a brand new rip or encode of the album. If you have the original torrent files for the inactive torrent, you should reseed those original files instead of uploading a new torrent.
The process of replacing a torrent that does not follow the rules with a torrent that does follow the rules is called trumping. The most common trumps are format trumps, tag trumps, and folder trumps.
The following chart shows the hierarchy of format trumps.
At the top of each column but the one on the left are formats that can never be trumped. We recommend that you only upload in these formats in order to prevent your torrents from being trumped by other users. If you have the release in lossless/FLAC, we recommend uploading only FLAC, 320 and V0, as these formats will never be trumped by "better" formats. If you only have the release in some other lossy format/bitrate, e.g. MP3 CBR 224 or AAC 256, then feel free to upload it as long as no "better" formats already exist on the site, but understand that your upload may be trumped in the future. Never transcode your lossy files to FLAC, 320 or V0 to prevent them from being format trumped, as the consequences for uploading transcodes are much, much worse.
Lossy Format Trump Rules
- If there is no existing torrent of the album in the allowed format you've chosen, you may upload it in any bitrate that averages at least 192 kbps. (This does not apply to V0 - V2 releases)
- You may always upload MP3 V0 or MP3 320kbps (CBR) as long as another rip with the same bitrate and format doesn't already exist.
- Higher bitrate CBR (Constant Bitrate) and ABR (Average Bitrate) torrents replace lower ones. Once a CBR rip has been uploaded, no CBR rips of that bitrate or lower can be uploaded. In the same manner, once an ABR rip has been uploaded, no ABR rips of that bitrate or lower can be uploaded.
- AAC encodes can be trumped by any allowed MP3 format of the same edition and media. (This does not apply to AAC torrents with files bought from the iTunes Store that contain iTunes Exclusive tracks.)
- Lossy format torrents with .log files, .cue files, .m3u files, and album artwork do not replace equivalent existing torrents.
Lossless Format Trump Rules
- Rips must be taken from commercially pressed or official (artist- or label-approved) CD sources. They may not come from CD-R copies of the same pressed CDs (unless the release was only distributed on CD-R by the artist or label).
- A FLAC torrent without a log (or with a log from a non-EAC or non-XLD ripping tool like dBpoweramp or Rubyripper) may be trumped by a FLAC torrent with a log from an approved ripping tool with any score.
- A FLAC upload with an EAC or XLD log that scores 100% on the log checker replaces one with a lower score. However, no log scoring less than 100% can trump an already existing one that scores under 100% (for example, a rip with a 99% log cannot replace a rip with an 80% log).
- A 100% log rip without a cue sheet can be replaced by a 100% log rip with a noncompliant cue sheet ONLY when the included cue sheet is materially different from "a cue generated from the ripping log." Examples of a material difference include additional or correct indices, properly detected pre-gap lengths, and pre-emphasis flags.
Tag trumps happen when the original torrent either doesn't have the required tag fields or the information in one of the tag fields is completely wrong or misspelled. In the case of misspelled words, the spelling must be entirely off in order for the tag trump to be considered (for example, missing prepositions like "the" or "a", or a couple letters being in the wrong order like "lvoe" instead of "love" is not enough for a tag trump).
- The required tag fields are: title, album, artist, track number.
- Torrent album titles must accurately reflect the actual album titles. Use proper capitalization when naming your albums. Typing the album titles in all lowercase letters or all capital letters is unacceptable and makes the torrent trumpable.
- Newly re-tagged torrents trumping badly tagged torrents must reflect a substantial improvement over the previous tags. Small changes that include replacing ASCII characters with proper foreign language characters with diacritical marks (á, é, í, ó, ú, etc.), fixing slight misspellings, or missing an alternate spelling of an artist (excluding "The" before a band name) are not enough for replacing other torrents.
Folder trumps happen when the original torrent's folder is not named like it should be. Folders should at the very least include the album name, but should hopefully also include the year released and music format. Nested folders are also not allowed.
- Music releases must be in a directory that contains the music. This includes single track releases, which must be enclosed in a torrent folder even if there is only one file in the torrent. No music may be compressed in an archive (.rar, .zip, .tar, .iso).
- Name your directories with meaningful titles, such as "Artist - Album (Year) - Format." The minimum acceptable is "Album" although you should include more information.
- Avoid creating unnecessary nested folders (such as an extra folder for the actual album) inside your properly named directory.
- File names must accurately reflect the song titles. You may not have file names like 01track.mp3, 02track.mp3, etc. Torrents containing files that are named with incorrect song titles can be trumped by properly labeled torrents.
- Multiple-disc torrents cannot have tracks with the same numbers in one directory. You may place all the tracks for Disc One in one directory and all the tracks for Disc Two in another directory or prepend your file names with disc numbers, e.g. 1-01 - first track title.mp3, etc. if you put all the files in a single folder.