From 0b0c229b4aa4fcce9dcced9610d37bd101f0867b Mon Sep 17 00:00:00 2001 From: Git Date: Sun, 9 Sep 2012 08:00:26 +0000 Subject: [PATCH] Empty commit --- INSTALL.txt | 8 +- classes/script_start.php | 53 ++++---- design/privateheader.php | 4 +- sections/artist/artist.php | 4 +- sections/blog/index.php | 2 +- sections/bookmarks/torrents.php | 14 +-- sections/chat/index.php | 45 ++++--- sections/collages/collage.php | 16 +-- sections/error/index.php | 6 +- sections/forums/search.php | 4 +- sections/forums/take_warn.php | 2 +- sections/forums/thread.php | 14 ++- sections/friends/friends.php | 2 +- sections/inbox/compose.php | 2 +- sections/index/private.php | 2 +- sections/log/index.php | 2 +- sections/login/recover_step1.php | 8 +- sections/login/recover_step2.php | 6 +- sections/register/code.php | 2 +- sections/register/index.php | 2 +- sections/register/step1.php | 10 +- sections/reports/report.php | 2 +- sections/reports/reports.php | 2 +- sections/reports/takereport.php | 2 +- sections/reportsv2/ajax_report.php | 10 +- sections/reportsv2/array.php | 6 +- sections/reportsv2/takeresolve.php | 2 +- sections/requests/new_edit.php | 4 +- sections/requests/requests.php | 18 ++- sections/requests/takefill.php | 22 ++-- sections/requests/takeunfill.php | 6 +- sections/rules/upload.php | 123 ++++++++++--------- sections/schedule/index.php | 10 +- sections/staff/index.php | 2 +- sections/staffblog/index.php | 2 +- sections/staffpm/common_responses.php | 10 +- sections/staffpm/functions.php | 6 +- sections/staffpm/makedonor.php | 4 +- sections/staffpm/user_inbox.php | 2 +- sections/staffpm/viewconv.php | 18 +-- sections/stats/torrents.php | 2 +- sections/stats/users.php | 16 +-- sections/tools/managers/tag_aliases.php | 4 +- sections/tools/managers/tokens.php | 4 +- sections/torrents/browse2.php | 4 +- sections/torrents/details.php | 10 +- sections/torrents/notify.php | 4 +- sections/upload/upload_handle.php | 2 +- sections/user/advancedsearch.php | 8 ++ sections/user/edit.php | 8 +- sections/user/index.php | 6 +- sections/user/invite.php | 4 +- sections/user/linkedfunctions.php | 4 +- sections/user/notify_edit.php | 4 +- sections/user/takeedit.php | 2 +- sections/user/takemoderate.php | 24 ++-- sections/user/user.php | 6 +- sections/userhistory/email_history2.php | 6 +- sections/userhistory/ip_history.php | 6 +- sections/userhistory/passkey_history.php | 4 +- sections/userhistory/password_history.php | 4 +- sections/userhistory/subscribed_collages.php | 8 +- sections/userhistory/token_history.php | 2 +- sections/wiki/aliases.php | 2 +- sections/wiki/compare.php | 2 +- sections/wiki/revisions.php | 2 +- sections/wiki/search.php | 6 +- sections/wiki/splash.php | 4 +- sections/wiki/takecreate.php | 2 +- sections/wiki/wiki_browse.php | 25 ++-- 70 files changed, 340 insertions(+), 304 deletions(-) diff --git a/INSTALL.txt b/INSTALL.txt index ef75c920..55d5b8d6 100644 --- a/INSTALL.txt +++ b/INSTALL.txt @@ -1,17 +1,17 @@ INSTALLATION NOTES 1. Set up MySQL and memcached. We run memcached with the command: memcached -d -m 5120 -s /var/run/memcached.sock -a 0777 -t16 -C -u root - This gives it 5 gigs of RAM, you probably want to set that a bit lower! + This gives it 5 gigs of RAM; you probably want to set that a bit lower! 2. Run gazelle.sql (preferably as root) to create the database, the table, and the default data. 3. Install sphinx - we recommend you use the included sphinx.conf For documentation, read http://www.sphinxsearch.com/docs/current.html - After you've installed, create the indices: + After you've installed sphinx, create the indices: /usr/local/bin/indexer -c /etc/sphinx/sphinx.conf --all 4. Move classes/config.template to classes/config.php. Edit the config.php as needed. We use http://grc.com/passwords.html for our passwords - you'll be generating a lot of these. -5. Sign up. The first user is made a sysop! +5. Sign up. The first user is made a SysOp! 6. Set up cron jobs. You need a cron job for the schedule, a cron job for the peerupdate (all groups are cached, but the peer counts change often, so peerupdate is a script to update them), and the two sphinx indices. @@ -23,7 +23,7 @@ These are our cron jobs: 5 0,12 * * * /usr/local/bin/indexer -c /etc/sphinx/sphinx.conf --rotate --all 7. You're probably going to want geoip information, so first you need to fill in the geoip_country tables by visiting /tools.php?action=update_geoip . - After that finishes parsing information from maxmind, you'll may want to map users to countries by running: + After that finishes parsing information from maxmind, you may want to map users to countries by running: "INSERT INTO users_geodistribution (Code, Users) SELECT g.Code, COUNT(u.ID) AS Users FROM geoip_country AS g JOIN users_main AS u ON INET_ATON(u.IP) BETWEEN g.StartIP AND g.EndIP WHERE u.Enabled='1' GROUP BY g.Code ORDER BY Users DESC" This will fill in the table needed for stats. diff --git a/classes/script_start.php b/classes/script_start.php index 3684eddc..63a89375 100644 --- a/classes/script_start.php +++ b/classes/script_start.php @@ -1212,22 +1212,19 @@ function format_username($UserID, $Badges = false, $IsWarned = true, $IsEnabled return "Unknown [$UserID]"; } - $str = ''; + $Str = ''; if ($Title) { - $str .= ''; - } - - $str.=''.$UserInfo['Username'].''; - if ($Title) { - $str .= ''; + $Str .= ''.$UserInfo['Username'].''; + } else { + $Str .= ''.$UserInfo['Username'].''; } if ($Badges) { - $str.=($UserInfo['Donor'] == 1) ? 'Donor' : ''; + $Str .= ($UserInfo['Donor'] == 1) ? 'Donor' : ''; } - $str.=($IsWarned && $UserInfo['Warned']!='0000-00-00 00:00:00') ? 'Warned' : ''; - $str.=($IsEnabled && $UserInfo['Enabled'] == 2) ? 'Banned' : ''; + $Str .= ($IsWarned && $UserInfo['Warned'] != '0000-00-00 00:00:00') ? 'Warned' : ''; + $Str .= ($IsEnabled && $UserInfo['Enabled'] == 2) ? 'Banned' : ''; if ($Badges) { $ClassesDisplay = array(); @@ -1236,30 +1233,34 @@ function format_username($UserID, $Badges = false, $IsWarned = true, $IsEnabled $ClassesDisplay[] = ''.$PermHTML.''; } } - $str .= ((!empty($ClassesDisplay))?' ':'').implode(' ', $ClassesDisplay); + if(!empty($ClassesDisplay)) { + $Str .= implode(' ', $ClassesDisplay); + } } - if ($Title && $Class) { - $str .= ''; - } - $str.=($Class) ? ' ('.make_class_string($UserInfo['PermissionID']).')' : ''; - if ($Title && $Class) { - $str .= ''; + if ($Class) { + if ($Title) { + $Str .= ' ('.make_class_string($UserInfo['PermissionID']).')'; + } else { + $Str .= ' ('.make_class_string($UserInfo['PermissionID']).')'; + } } + if ($Title) { // Image proxy CTs if(check_perms('site_proxy_images') && !empty($UserInfo['Title'])) { - $UserInfo['Title'] = preg_replace_callback('~src=("?)(http.+?)(["\s>])~', function($Matches) { - return 'src='.$Matches[1].'http'.($SSL?'s':'').'://'.SITE_URL.'/image.php?c=1&i='.urlencode($Matches[2]).$Matches[3]; - }, $UserInfo['Title']); + $UserInfo['Title'] = preg_replace_callback('~src=("?)(http.+?)(["\s>])~', + function($Matches) { + return 'src='.$Matches[1].'http'.($SSL?'s':'').'://'.SITE_URL.'/image.php?c=1&i='.urlencode($Matches[2]).$Matches[3]; + }, + $UserInfo['Title']); } - $str.=''; if ($UserInfo['Title']) { - $str.= ' ('.$UserInfo['Title'].')'; + $Str .= ' ('.$UserInfo['Title'].')'; } } - return $str; + return $Str; } function make_class_string($ClassID) { @@ -2436,7 +2437,7 @@ function freeleech_groups($GroupIDs, $FreeNeutral = 1, $FreeLeechType = 0) { /** * Used to check if keys in $_POST and $_GET are all set - * This reduces if statement redundancy for alot of variables + * This reduces 'if' statement redundancy for a lot of variables */ function isset_request($Request, $Keys=NULL, $AllowEmpty = False, $Error=0) { if(isset($Keys)) { @@ -2468,9 +2469,9 @@ function isset_request($Request, $Keys=NULL, $AllowEmpty = False, $Error=0) { $Debug->set_flag('completed module execution'); /* Required in the absence of session_start() for providing that pages will change -upon hit rather than being browser cache'd for changing content. +upon hit rather than being browser cached for changing content. -Old versions of Internet explorer choke when downloading binary files over HTTPS with disabled cache. +Old versions of Internet Explorer choke when downloading binary files over HTTPS with disabled cache. Define the following constant in files that handle file downloads */ if(!defined('IE_WORKAROUND_NO_CACHE_HEADERS')) { header('Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0'); diff --git a/design/privateheader.php b/design/privateheader.php index 1bb68e28..e6055749 100644 --- a/design/privateheader.php +++ b/design/privateheader.php @@ -122,7 +122,7 @@
  • Required:
    • 0) { ?> -
  • Tokens:
    • +
  • Tokens:
    • - + 0) && ($Torrent['Size'] < 1073741824) && !in_array($TorrentID, $TokenTorrents) && empty($Torrent['FreeTorrent']) && ($LoggedUser['CanLeech'] == '1')) { ?> - | FL + | FL ]   »  diff --git a/sections/blog/index.php b/sections/blog/index.php index d84389ad..6eaf7a62 100644 --- a/sections/blog/index.php +++ b/sections/blog/index.php @@ -156,7 +156,7 @@ full_format($Body)?>

    - Discuss this post here + Discuss this post here [Remove link] [ DL 0) && ($Torrent['Size'] < 1073741824) && !in_array($TorrentID, $TokenTorrents) && empty($Torrent['FreeTorrent']) && ($LoggedUser['CanLeech'] == '1')) { ?> - | FL + | FL | RP ] @@ -242,7 +242,7 @@ function compare($X, $Y){ [ DL 0) && ($Torrent['Size'] < 1073741824) && !in_array($TorrentID, $TokenTorrents) && empty($Torrent['FreeTorrent']) && ($LoggedUser['CanLeech'] == '1')) { ?> - | FL + | FL | RP ] @@ -392,14 +392,14 @@ function compare($X, $Y){ $CollageCovers) { ?> - +//]]>
    +
    +

    Uploading

    +
    +
    Example: The search term FLAC returns all rules containing FLAC. The search term FLAC+trump returns all rules containing both FLAC and trump.
    @@ -58,7 +62,7 @@
  • 2. Music
    • @@ -106,7 +110,7 @@

    ↑ Introduction

    The uploading rules below are overwhelmingly long and detailed for a reason. The length is necessary to explain the rules clearly and thoroughly. A summary of each rule is in bold text before the actual rule for easier reading. You may also find the corresponding rule sections in the Index. The corresponding ↑ (move one level up) and rule section links (move down into the document) help provide quick navigation.

    -

    Before you upload anything, if you are still unsure of what a rule means, PLEASE ask your questions at any of the following points of site user support: First-Line Support, The Help Forum, or #what.cd-help on IRC. Privately message a moderator on the site if other support has directed you to a moderator or if support has been unhelpful in your particular case. If you find any dead links in the upload rules, let a staff member know so it can be promptly fixed.

    +

    Before you upload anything, if you are still unsure of what a rule means, PLEASE ask your questions at any of the following points of site user support: First-Line Support, The Help Forum, or #what.cd-help on IRC. Privately message a moderator on the site if other support has directed you to a moderator or if support has been unhelpful in your particular case. If you find any dead links in the upload rules, let a staff member know so it can be promptly fixed.

    ↑ 1. Uploading Rules

    @@ -119,12 +123,13 @@
  • ↑_ 1.1.3. No freely available content in non-music sections. If you could just download something from the web, so can everyone else. Each main section explains in greater detail what "freely available" means in the context of that section. See 2.1.9 in regards to freely available music. See 4.1.3 in regards to freely available applications.
  • ↑_ 1.1.4. Seed complete copies of your uploads. Do not upload a torrent unless you intend to seed until there are at least 1.0 distributed copies. Seeding past this minimum is strongly encouraged.
  • ↑_ 1.1.5. No advertisements. Do not advertise other sites or groups in torrent descriptions, torrent directories, torrent file names, or torrent contents. We have no advertising and neither should you. Exceptions: Additional information about an artist, album, or band is acceptable, and is not considered advertising. Also, .nfo files in scene releases are not considered advertising.
    • -
  • ↑_ 1.1.6. Archived files in uploads are not allowed. Exceptions: The sections that allow archived files (e.g., zip, rar, iso, etc.) are the following:
    • +
  • ↑_ 1.1.6. Archived files in uploads are not allowed. Exceptions: The sections that allow archived files (e.g., zip, rar, iso, etc.) are the following:
    • Comic Books (.cbr and .cbz).
    • Scene released torrents in non-music categories.
    • Sheet music may be individually archived.
    +
    • ↑ 1.2. Specifically Banned
    @@ -167,16 +172,16 @@
  • ↑_ 2.1.2. No transcodes or re-encodes of lossy releases are acceptable here.
      -
    • ↑_ 2.1.2.1. The only acceptable transcodes are releases that were transcoded from a lossless source (e.g., CD, SBD, DAT, Vinyl, SACD, or LPCM). Please refer to this wiki for more information on transcodes and how to detect them.
      • -
    • ↑_ 2.1.2.2. Official lossy-mastered releases are not considered transcodes. They are allowed on the site. See this wiki for further information.
      • +
    • ↑_ 2.1.2.1. The only acceptable transcodes are releases that were transcoded from a lossless source (e.g., CD, SBD, DAT, Vinyl, SACD, or LPCM). Please refer to this wiki for more information on transcodes and how to detect them.
      • +
    • ↑_ 2.1.2.2. Official lossy-mastered releases are not considered transcodes. They are allowed on the site. See this wiki for further information.
    • ↑_ 2.1.2.3. Releases from Bandcamp, Beatport, and similar online retailers are considered official lossy-mastered releases when lossy mastered by the artist or label. A non-lossy mastered release from any source may trump a lossy mastered release from a WEB source. And if the same WEB retailer revises their release and subsequently supplies a non-lossy mastered release, the new source may trump the original upload.
    • -
  • ↑_ 2.1.3. Music releases must have an average bitrate of at least 192 kbps regardless of the format. Exceptions: The following VBR encodes may go under the 192 kbps limit: LAME V2 (VBR), V1 (VBR), V0 (VBR), APS (VBR), APX (VBR), MP3 192 (VBR), and AAC ~192 (VBR) to AAC ~256 (VBR) releases. See this wiki for more information on encoding options.
    • -
  • ↑_ 2.1.4. Bitrates must accurately reflect encoder presets or the average bitrate of the audio files. You are responsible for supplying correct format and bitrate information on the upload page. See this wiki for further information.
    • +
  • ↑_ 2.1.3. Music releases must have an average bitrate of at least 192 kbps regardless of the format. Exceptions: The following VBR encodes may go under the 192 kbps limit: LAME V2 (VBR), V1 (VBR), V0 (VBR), APS (VBR), APX (VBR), MP3 192 (VBR), and AAC ~192 (VBR) to AAC ~256 (VBR) releases. See this wiki for more information on encoding options.
    • +
  • ↑_ 2.1.4. Bitrates must accurately reflect encoder presets or the average bitrate of the audio files. You are responsible for supplying correct format and bitrate information on the upload page. See this wiki for further information.
  • ↑_ 2.1.5. Albums must not be ripped or uploaded as a single track.
      -
    • ↑_ 2.1.5.1. If the tracks on the original CD were separate, you must rip them to separate files. Unsplit rips may be present on the site but are NOT the preferred format for lossless rips. Any unsplit FLAC rips lacking a cue sheet will be deleted outright. Any unsplit FLAC rip that includes a cue sheet will be trumpable by a properly split FLAC torrent. CDs with single tracks can be uploaded without prior splitting. See this wiki for information on unsplit rips. Information about splitting rips can be found here. Users who upload unsplit rips will be warned.
      • +
    • ↑_ 2.1.5.1. If the tracks on the original CD were separate, you must rip them to separate files. Unsplit rips may be present on the site but are NOT the preferred format for lossless rips. Any unsplit FLAC rips lacking a cue sheet will be deleted outright. Any unsplit FLAC rip that includes a cue sheet will be trumpable by a properly split FLAC torrent. CDs with single tracks can be uploaded without prior splitting. See this wiki for information on unsplit rips. Information about splitting rips can be found here. Users who upload unsplit rips will be warned.
    • ↑_ 2.1.5.2. Gapless DJ or professional mixes released as MP3+CUE images are allowed as unseparated album images on the site. This includes scene DJ mixes. You cannot take a previously split collection of tracks and upload it as an unsplit mix because the original form of those audio tracks was not a single unsplit file. Such torrents will be removed when reported. Split and unsplit versions do not count as duplicates of one another and may coexist.
    • ↑_ 2.1.5.3. For albums that contain separate tracks, unsplit MP3 albums are allowed for continuous albums and mixes only and must include a cue sheet. If there is no reason for the album to be uploaded unsplit, or if the torrent is lacking a cue sheet, it will be deleted. Exception: If the retail version of an unsplit MP3 album is sold without a cue sheet, you may upload the unsplit rip without a cue sheet.
    @@ -192,18 +197,18 @@
  • ↑_ 2.1.8. Music not sourced from vinyl must not contain pops, clicks, or skips. They will be deleted for rip/encode errors if reported. Music sourced from vinyl must follow the rules found here.
  • ↑_ 2.1.9. Freely available music is allowed. Uploaded music may be freely available on the web (come from official sources such as record labels, band websites, or the Internet Archive). Uploads can come from other torrent sites, but you are responsible for determining the audio quality of the music (i.e., that it is not transcoded, that it does not contain an edited log, that it is not a user compilation, etc.). Users are highly encouraged to provide a link to the source of their upload when uploading freely available music. However, this is not required and the lack of such a link to further information is not grounds for reporting a torrent. All freely available music must conform to both quality rules and formatting rules. This means it must be tagged correctly, not be a transcode, have separate tracks, and so forth. Freely available music uploads should have the "WEB" media format if no other source media (e.g., CD, DVD, etc.) can be established for the files.
  • ↑_ 2.1.10. Clearly label water-marked or voice-over releases. Watermarks or voice-overs must be clearly indicated in the torrent description. The torrent will be deleted for quality misrepresentation if this information is not noted.
    • -
  • ↑_ 2.1.11. Music ripped from the radio (Satellite or FM), television, the web, or podcasts are not allowed. See this wiki for the difference between web rips and the WEB category.
    • +
  • ↑_ 2.1.11. Music ripped from the radio (Satellite or FM), television, the web, or podcasts are not allowed. See this wiki for the difference between web rips and the WEB category.
  • ↑_ 2.1.12. No unofficial audience recordings may be uploaded. These include but are not limited to AUD (Audience), IEM (In Ear Monitor), ALD (Assistive Listening Device), Mini-Disc, and Matrix-sourced recordings (see 2.6.3).
  • ↑_ 2.1.13. Tape (VHS, Video-8, etc.) music sources are not allowed, except for cassette rips and certain soundboards. See 2.6 for further information.
    • -
  • ↑_ 2.1.14. The WEB media category is for digital downloads only. Digital downloads released only on the internet from internet sources cannot be given the CD media label on the upload page. This includes downloads from the iTunes Store, LiveDownloads, Beatport, Amazon.com, Rhapsody, and other web stores. Scene releases with no source information must be labeled as WEB. Freely available music with no source information must also be labeled as WEB. If possible, indicate the source of your files (e.g., the specific web store) in the torrent description. You are responsible for determining whether the downloaded files conform to What.CD's rules for music quality. Note: Do not confuse WEB-sourced files with web rips (see this wiki). WEB media torrents are not always web rips (meaning transcodes). Please check the spectrals before assuming that they are web rips.
    • +
  • ↑_ 2.1.14. The WEB media category is for digital downloads only. Digital downloads released only on the internet from internet sources cannot be given the CD media label on the upload page. This includes downloads from the iTunes Store, LiveDownloads, Beatport, Amazon.com, Rhapsody, and other web stores. Scene releases with no source information must be labeled as WEB. Freely available music with no source information must also be labeled as WEB. If possible, indicate the source of your files (e.g., the specific web store) in the torrent description. You are responsible for determining whether the downloaded files conform to What.CD's rules for music quality. Note: Do not confuse WEB-sourced files with web rips (see this wiki). WEB media torrents are not always web rips (meaning transcodes). Please check the spectrals before assuming that they are web rips.
  • ↑_ 2.1.15. WEB uploads must be uploaded at the bit depths and sampling rates they were sold at. WEB uploads of the same audio with different sampling rates or bit depths may coexist if that is how they are sold or distributed. This means that if, for example, an album is sold with a bit depth of 24 bits and a sampling rate of 88.2 kHz, it must be uploaded directly with no modifications to the audio stream. An existing WEB upload of the same material with a bit depth of 24 and a sampling rate of 96 kHz may coexist with the new 24/88.2 upload but does not trump it. See 2.1.6.2 for more information.
  • ↑_ 2.1.16. User-made compilations are not allowed.
      -
    • ↑_ 2.1.16.1. These are defined as compilations made by the uploader or anyone else who does not officially represent the artist or the label. Compilations must be reasonably official. For example, "34 of my favourite Grateful Dead songs" is not a reasonably official collection. Compiling a release from a list, such as a Top 100 Billboard Chart, is not allowed. User-made and unofficial multichannel mixes are also not allowed. See this wiki for more information.
      • +
    • ↑_ 2.1.16.1. These are defined as compilations made by the uploader or anyone else who does not officially represent the artist or the label. Compilations must be reasonably official. For example, "34 of my favourite Grateful Dead songs" is not a reasonably official collection. Compiling a release from a list, such as a Top 100 Billboard Chart, is not allowed. User-made and unofficial multichannel mixes are also not allowed. See this wiki for more information.
    • ↑_ 2.1.16.2. Exceptions: Bootlegs are allowed if they meet quality standards for music and are proven to be retail releases in either a digital or physical form. Bootlegs/mixtapes assembled and available from internet-only sources (e.g., music blogs, message boards, etc.) are not considered official enough for this site.
    • -
  • ↑_ 2.1.17. No comedy, audiobook, or spoken word releases may be uploaded as music. These torrents must not be grouped with other formats from the same release (i.e., they need to have individual torrent pages). See 3.2 and this wiki for more information.
    • +
  • ↑_ 2.1.17. No comedy, audiobook, or spoken word releases may be uploaded as music. These torrents must not be grouped with other formats from the same release (i.e., they need to have individual torrent pages). See 3.2 and this wiki for more information.
  • ↑_ 2.1.18. Sound Sample Packs must be uploaded as applications. See 4.1.9 for more information.
  • ↑_ 2.1.19. All music torrents must represent a complete release, and may not be missing tracks (or discs in the case of a multi-disc release).
      @@ -213,21 +218,21 @@
  • ↑_ 2.1.20. User made discographies may not be uploaded. Multi-album torrents are not allowed on the site under any circumstances. That means no discographies, Pitchfork compilations, etc. If releases (e.g., CD singles) were never released as a bundled set, do not upload them together. Live Soundboard material should be uploaded as one torrent per night, per show, or per venue. Including more than one show in a torrent results in a multi-album torrent. Exceptions: Only official boxsets and official compilation collections can contain multiple albums.
    • -
  • ↑_ 2.1.21. Pre-emphasis is allowed in lossless torrents only. Lossless FLAC torrents with pre-emphasis are allowed on the site. They are allowed to coexist with lossless de-emphasized torrents (both in their separate album edition groups). In contrast, lossy formats may not have pre-emphasis and will be deleted if uploaded.
    • -
  • ↑_ 2.1.22. Edition Information must be provided for digitally-sourced torrents. Digitally-sourced (including CD-sourced) rips of albums that were first released before the availability of their source medium must have accurate edition information. For example, if a CD rip is of an album whose original release date was 1957, predating the creation and distribution of CDs, then the uploader must make note of the correct year in which the CD was pressed, and preferably note the catalog identification as well. Rips for which Edition Information cannot be provided must be marked as an "Unknown Release." Under no circumstances may you guess or feign knowledge of the Edition Information. See this wiki for more information on album editions.
    • -
  • ↑_ 2.1.23. This audio layer must comply with the Redbook standard for audio data. If there is no Redbook audio on the game disc, you may not upload a rip of the disc. Be prepared to provide extensive information on any audio that is ripped from a gaming disc (see this wiki for information about providing proofs). +
  • ↑_ 2.1.21. Pre-emphasis is allowed in lossless torrents only. Lossless FLAC torrents with pre-emphasis are allowed on the site. They are allowed to coexist with lossless de-emphasized torrents (both in their separate album edition groups). In contrast, lossy formats may not have pre-emphasis and will be deleted if uploaded.
    • +
  • ↑_ 2.1.22. Edition Information must be provided for digitally-sourced torrents. Digitally-sourced (including CD-sourced) rips of albums that were first released before the availability of their source medium must have accurate edition information. For example, if a CD rip is of an album whose original release date was 1957, predating the creation and distribution of CDs, then the uploader must make note of the correct year in which the CD was pressed, and preferably note the catalog identification as well. Rips for which Edition Information cannot be provided must be marked as an "Unknown Release." Under no circumstances may you guess or feign knowledge of the Edition Information. See this wiki for more information on album editions.
    • +
  • ↑_ 2.1.23. This audio layer must comply with the Redbook standard for audio data. If there is no Redbook audio on the game disc, you may not upload a rip of the disc. Be prepared to provide extensive information on any audio that is ripped from a gaming disc (see this wiki for information about providing proofs).
      -
    • ↑_ 2.1.23.1. This audio layer must comply with the Redbook standard for audio data. f there is no Redbook audio on the game disc, you may not upload a rip of the disc. Be prepared to provide extensive information on any audio that is ripped from a gaming disc (see +
    • ↑_ 2.1.23.1. This audio layer must comply with the Redbook standard for audio data. f there is no Redbook audio on the game disc, you may not upload a rip of the disc. Be prepared to provide extensive information on any audio that is ripped from a gaming disc (see this wiki for information about providing proofs).
    • ↑_ 2.1.23.2. The audio must meet the minimum requirements for music on the site (see 2.1.3 and 2.1.6).
    • ↑_ 2.1.23.3. Officially-released game soundtracks, which adhere to Redbook standards, are always allowed.
  • ↑_ 2.1.24. Lossy AAC torrents may only be uploaded when they represent exclusive content not currently available in any other format (e.g., an iTunes WEB exclusive release).
    • -
  • ↑_ 2.1.25. No HDCD content may be uploaded to the site. There are inherent problems with ripping this format, and other forms of high-resolution audio are both more prevalent and preferred at this time (i.e., vinyl, SACD, Blu-ray, etc.). Any CD bearing the HDCD logo can still be ripped using the usual methods for ripping normal audio CDs. See this wiki for more details on the media format.
    • +
  • ↑_ 2.1.25. No HDCD content may be uploaded to the site. There are inherent problems with ripping this format, and other forms of high-resolution audio are both more prevalent and preferred at this time (i.e., vinyl, SACD, Blu-ray, etc.). Any CD bearing the HDCD logo can still be ripped using the usual methods for ripping normal audio CDs. See this wiki for more details on the media format.
  • ↑_ 2.1.26. Downsampling of digital sources is allowed for certain media types. Downsampling of CD sources is strictly prohibited. Downsampling of WEB sources is allowed for audio files sampled at 96 kHz and above. If the WEB source is already sampled at a rate of either 44.1 kHz or 48 kHz you may not downsample the audio files any further. Downsampling of SACD, DVD, or Blu-ray sources is allowed in certain cases. See 2.8.5, 2.7.3, and 2.9.5 for more information.
    • -
    ↑ 2.2. Duplicates & Trumping
    +
    ↑ 2.2. Duplicates & Trumping
    • ↑_ 2.2.0. Overview @@ -243,10 +248,10 @@
    • ↑_ 2.2.5. Scene and non-scene torrents for the same release, in the same bitrate and format, are dupes. The Scene label does not make the torrents unique from one another. If a scene V2 (VBR) of an album from CD is already uploaded, you may not upload another V2 (VBR) of the same album from CD.
    • ↑_ 2.2.6. All vinyl torrents must be ripped at the correct speed. You must rip all vinyl albums at the speed with which they were intended to be played (see 2.5.7).
    • ↑_ 2.2.7. Complete or untouched releases replace incomplete or watermarked versions. Watermarked promos containing voice-overs and similar imperfections can be trumped by a non-watermarked release. Releases missing hidden or pre-gap tracks can be replaced by proper rips that include the entire range of tracks. These hidden or pre-gap tracks should be in their own file, not appended to the beginning of track one. Releases where the hidden or pre-gap track is appended to the first track can be trumped by one where the track is in a separate file.
      • -
    • ↑_ 2.2.8. Torrents that have been inactive (e.g., not seeded) for two weeks may be trumped by the identical torrent (e.g., reseeded) or by a brand new rip or encode (see this wiki for the torrent inactivity rules) of the album. If you have the original torrent files for the inactive torrent, it is preferable to reseed those original files instead of uploading a new torrent. Uploading a replacement torrent should be done only when the files from the original torrent cannot be recovered or are unavailable.
      • +
    • ↑_ 2.2.8. Torrents that have been inactive (e.g., not seeded) for two weeks may be trumped by the identical torrent (e.g., reseeded) or by a brand new rip or encode (see this wiki for the torrent inactivity rules) of the album. If you have the original torrent files for the inactive torrent, it is preferable to reseed those original files instead of uploading a new torrent. Uploading a replacement torrent should be done only when the files from the original torrent cannot be recovered or are unavailable.
    • ↑_ 2.2.9. Lossy rules
        -
      • ↑_ 2.2.9.1. Higher bitrate CBR (Constant Bitrate) and ABR (Average Bitrate) torrents replace lower ones. Once a CBR (Constant Bitrate) rip has been uploaded, no CBR rips of that bitrate or lower can be uploaded. In the same manner, once an ABR (Average Bitrate) rip has been uploaded, no ABR rips of that bitrate or lower can be uploaded. For example, if a 320 kbps CBR rip is already on the site, you are not allowed to upload a 256 kbps CBR. ABR and CBR may be interchangeably trumped. A CBR can trump a lower bitrate ABR and an ABR may trump a lower bitrate CBR. You may not upload a 192 kbps CBR if a 256 kbps ABR of the same release is already up. See this wiki for more information.
        • +
      • ↑_ 2.2.9.1. Higher bitrate CBR (Constant Bitrate) and ABR (Average Bitrate) torrents replace lower ones. Once a CBR (Constant Bitrate) rip has been uploaded, no CBR rips of that bitrate or lower can be uploaded. In the same manner, once an ABR (Average Bitrate) rip has been uploaded, no ABR rips of that bitrate or lower can be uploaded. For example, if a 320 kbps CBR rip is already on the site, you are not allowed to upload a 256 kbps CBR. ABR and CBR may be interchangeably trumped. A CBR can trump a lower bitrate ABR and an ABR may trump a lower bitrate CBR. You may not upload a 192 kbps CBR if a 256 kbps ABR of the same release is already up. See this wiki for more information.
      • ↑_ 2.2.9.2. Lossy format torrents with .log files do not replace equivalent existing torrents. If you want to upload a lossy format (e.g., MP3) torrent that contains a log, when that format already exists in the same medium and album edition (but without the log), your new torrent will be considered a dupe. For example, a V2 (VBR) MP3 torrent with a log cannot replace a V2 (VBR) MP3 without a log. The same standard applies for lossy audio torrents with .m3u, .cue, and other additions such as artwork. Exceptions: If an existing torrent contains encode/rip errors, you may upload another copy that does not have errors. The bad torrent needs to be reported (with clear information about which tracks and what time points are affected) or your torrent will be deleted as a dupe. Also, see 2.3.8 through 2.3.16 for replacing poorly named and tagged torrents.
      • ↑_ 2.2.9.3. V0 (VBR), V2 (VBR), and 320 CBR MP3 are allowed at any time. You may upload a V0 (VBR), V2 (VBR) or 320 CBR MP3 as long as another rip with the same bitrate and format doesn't already exist. So if a V0 (VBR) is on the site, you may still upload a V2 (VBR) or 320 CBR MP3 of the same release.
      • ↑_ 2.2.9.4. V2 (VBR) replaces APS (VBR), and both replace CBR rips under 256 kbps, 192 (ABR), and rips averaging 192 (VBR) to 210 (VBR). Once a rip with either the V2 (VBR) or APS (VBR) LAME encoding preset has been uploaded, you are not allowed to upload any CBR torrents under 256 kbps bitrate. Furthermore, a V2 (VBR) or APS (VBR) rip will trump all indiscriminate VBR rips of similar bitrate. A V2 (VBR) rip will replace a 192 (VBR) rip or 210 (VBR) rip, for example. Also, a V2 (VBR) will replace a 192 (ABR) torrent.
        • @@ -266,23 +271,23 @@
      • ↑_ 2.2.10.1. All FLAC CD rips must come from official CD sources.
        • ↑_ 2.2.10.1.1. Rips must be taken from commercially pressed or official (e.g., artist- or label-approved) CD sources. They may not come from CD-R copies of the same pressed CDs.
          • -
        • ↑_ 2.2.10.1.2. Exceptions: If the release is only distributed on CD-R by the label or artist, then that is acceptable. See this wiki for more information on CD-R releases.
          • +
        • ↑_ 2.2.10.1.2. Exceptions: If the release is only distributed on CD-R by the label or artist, then that is acceptable. See this wiki for more information on CD-R releases.
        • -
      • ↑_ 2.2.10.2. 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 that scores either 100% or <100% because of non-audio deductions. For example, an EAC log that scores 50% (because of CRC mismatches or other audio deductions) cannot trump a Rubyripper log. See this wiki for more information on approved ripping tools. Also, see this wiki for setting up EAC and this wiki for ripping with EAC. See this wiki for ripping with XLD. Please make sure the log file has the .log extension so that it can display properly on the torrent page.
        • -
      • ↑_ 2.2.10.3. A FLAC upload with an EAC or XLD rip log that scores 100% on the log checker replaces one with a lower score. No log scoring less than 100% can trump an already existing one that scores under 100%. For example, a FLAC+log rip that scores 50% in the log checker cannot be trumped by a FLAC+log rip that scores 80%. What.CD recommends this guide for EAC, and this guide for XLD. See this wiki for more information on the site log checker. Note: A FLAC upload with a log that scores 95% for not defeating the audio cache may be rescored to 100% following the procedure outlined in this wiki.
        • -
      • ↑_ 2.2.10.4. A FLAC upload with only non-audio deductions in the log (see this wiki) may replace a FLAC upload with a log that scores 0% or contains audio deductions. For example, a range rip that has AccurateRip scores of two or higher and assorted non-audio deductions (e.g., burst mode, audio cache, pre-gaps, C2 pointers, etc.) can trump a log that has audio deductions for mismatching CRCs.
        • +
      • ↑_ 2.2.10.2. 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 that scores either 100% or <100% because of non-audio deductions. For example, an EAC log that scores 50% (because of CRC mismatches or other audio deductions) cannot trump a Rubyripper log. See this wiki for more information on approved ripping tools. Also, see this wiki for setting up EAC and this wiki for ripping with EAC. See this wiki for ripping with XLD. Please make sure the log file has the .log extension so that it can display properly on the torrent page.
        • +
      • ↑_ 2.2.10.3. A FLAC upload with an EAC or XLD rip log that scores 100% on the log checker replaces one with a lower score. No log scoring less than 100% can trump an already existing one that scores under 100%. For example, a FLAC+log rip that scores 50% in the log checker cannot be trumped by a FLAC+log rip that scores 80%. What.CD recommends this guide for EAC, and this guide for XLD. See this wiki for more information on the site log checker. Note: A FLAC upload with a log that scores 95% for not defeating the audio cache may be rescored to 100% following the procedure outlined in this wiki.
        • +
      • ↑_ 2.2.10.4. A FLAC upload with only non-audio deductions in the log (see this wiki) may replace a FLAC upload with a log that scores 0% or contains audio deductions. For example, a range rip that has AccurateRip scores of two or higher and assorted non-audio deductions (e.g., burst mode, audio cache, pre-gaps, C2 pointers, etc.) can trump a log that has audio deductions for mismatching CRCs.
      • ↑_ 2.2.10.5. XLD and EAC logs in languages other than English require a manual log checker score adjustment by staff. The current log checker cannot parse non-English logs made by EAC and XLD. However, a special exception is made for foreign-language logs since the rip quality is equivalent to English logs. Please report your torrent with the RP link and select "Log Rescore Request" for the reason of the report so staff can check your torrent manually. Do not translate the log yourself (see 2.2.10.9).
      • ↑_ 2.2.10.6. Range rips of hidden tracks or regular range rips (acceptable under strict conditions) require manual score adjustment.
        • ↑_ 2.2.10.6.1. The new log checker cannot accurately score range-ripped hidden tracks appended to proper rip logs. If you have created a 100% rip with a hidden track, but the log checker has decreased your score for the hidden track, report the torrent and the log score will be corrected by staff.
        • ↑_ 2.2.10.6.2. If you created a CD range rip that has matching CRCs for test and copy, and where every track has an AccurateRip score of 2 or more, then you may submit your torrent for manual score adjustment. It will be rescored, assuming no other problems, to 99%.
          • -
        • ↑_ 2.2.10.6.3. The CD image rip must be split with CUETools, XLD, or EAC. No other splitter is acceptable for a score adjustment. You will not receive a score adjustment for copy-only range rips approved with AccurateRip, nor for range rips done with test and copy without AccurateRip enabled. See this wiki for information on splitting image rips with EAC.
          • +
        • ↑_ 2.2.10.6.3. The CD image rip must be split with CUETools, XLD, or EAC. No other splitter is acceptable for a score adjustment. You will not receive a score adjustment for copy-only range rips approved with AccurateRip, nor for range rips done with test and copy without AccurateRip enabled. See this wiki for information on splitting image rips with EAC.
        • -
      • ↑_ 2.2.10.7. A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet. See this wiki for more information on cue sheets. +
      • ↑_ 2.2.10.7. A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet. See this wiki for more information on cue sheets.
          -
        • ↑_ 2.2.10.7.1. 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. If you upload a torrent with a cue sheet that provides nothing additional beyond what is contained in the rip log of the preexisting torrent, it will be deleted as a dupe.
          • +
        • ↑_ 2.2.10.7.1. 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. If you upload a torrent with a cue sheet that provides nothing additional beyond what is contained in the rip log of the preexisting torrent, it will be deleted as a dupe.
        • ↑_ 2.2.10.7.2. Exceptions: An EAC 0.95 rip with a 100% log and no cue file, uploaded before September 14, 2010, may be trumped by a torrent that scores 100% under the current log checker requirements.
        • @@ -301,11 +306,11 @@
        • ↑_ 2.2.11.1. Different editions and source media count as separate releases.
            -
          • ↑_ 2.2.11.1.1. A rip from a different medium (e.g., vinyl) or release (e.g., a remaster) of an already existing torrent counts as a different edition. The dupe rules do not apply to the two different album editions, nor do they apply to two differently sourced torrents. So if a FLAC ripped from a CD is already up, you are still allowed to upload a FLAC ripped from vinyl. And if a 320 kbps CBR MP3 release for an original mastering of an album was uploaded, you are still allowed to upload a 320 kbps CBR MP3 remaster. See this wiki for the procedure on how to enter album edition information for a torrent.
            • +
          • ↑_ 2.2.11.1.1. A rip from a different medium (e.g., vinyl) or release (e.g., a remaster) of an already existing torrent counts as a different edition. The dupe rules do not apply to the two different album editions, nor do they apply to two differently sourced torrents. So if a FLAC ripped from a CD is already up, you are still allowed to upload a FLAC ripped from vinyl. And if a 320 kbps CBR MP3 release for an original mastering of an album was uploaded, you are still allowed to upload a 320 kbps CBR MP3 remaster. See this wiki for the procedure on how to enter album edition information for a torrent.
          • ↑_ 2.2.11.1.2. Only one edition of each unofficial live recording is allowed. See 2.6.2.
          • -
        • ↑_ 2.2.11.2. Rip log information (ToC, 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, label (imprint), or catalog number determine distinct releases. Though different editions may coexist, distinct releases that are not also distinct editions may not, and are considered dupes. See this wiki for more information.
          • +
        • ↑_ 2.2.11.2. Rip log information (ToC, 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, label (imprint), or catalog number determine distinct releases. Though different editions may coexist, distinct releases that are not also distinct editions may not, and are considered dupes. See this wiki for more information.
        • ↑_ 2.2.11.3. Multiple releases may be grouped into one edition. In such a case, torrents belonging to any of the releases determined to be in the same edition are considered dupes. Conversely, release groups may be split into more than one edition when it is determined that there is a material difference in audio content (different editions that have the same catalog information are known as "silent remasters"), in which case other formats may be uploaded for both editions.
        • ↑_ 2.2.11.4. Lossless uploads with edition information trump lossless rips with nonexistent or insufficient logs and no release information. An insufficient log is a log that doesn't provide any information (e.g., ToC, peak levels, and pre-gaps) about the audio being ripped.
        • ↑_ 2.2.11.5. If a lossless torrent has no release information (an "unknown release") but does have a log containing ToC, peak level, and pre-gap information, it cannot be trumped by a lossless torrent with release information unless the "lossless unknown release torrent" can be determined to be the same edition as a lossless torrent for which the release information is known. If such an identification can be made, the "lossless unknown release torrent" (and all lossy torrents that can be identified as transcodes of it) is moved into the same edition as the lossless torrent with edition information, and the merged torrents are then subject to dupe and trump rules as per 2.2.11.2. If the rip log is incomplete (missing ToC, peak level, or pre-gap information) and the information available matches a torrent in an edition whose release information is known, the torrent whose release information is known trumps the torrent whose release information is unknown.
          • @@ -323,10 +328,10 @@
        • ↑_ 2.3.1. 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 (e.g., .rar, .zip, .tar, .iso). Scene archives of music must be unpacked and not labeled as "scene."
        • ↑_ 2.3.2. Name your directories with meaningful titles, such as "Artist - Album (Year) - Format." The minimum acceptable is "Album" although it is preferable to include more information. If the directory name does not include this minimum then another user can rename the directory, re-upload, and report your torrent for deletion. In addition, torrent folders that are named using the scene convention will be trumpable if the Scene label is absent from the torrent.
        • ↑_ 2.3.3. Avoid creating unnecessary nested folders (such as an extra folder for the actual album) inside your properly named directory. A torrent with unnecessary nested folders is trumpable by a torrent with such folders removed. For single disc albums, all audio files must be included in the main torrent folder. For multi-disc albums, the main torrent folder may include one sub-folder that holds the audio file contents for each disc in the box set, i.e., the main torrent folder is "Adele - 19 (2008) - FLAC" while appropriate sub-folders may include "19 (Disc 1of2)" or "19" and "Live From The Hotel Cafe (Disc 2of2)" or "Acoustic Set Live From The Hotel Cafe, Los Angeles." Additional folders are unnecessary because they do nothing to improve the organization of the torrent. If you are uncertain about what to do for other cases, PM a staff member for guidance.
          • -
        • ↑_ 2.3.4. Label your torrents according to site standards. Follow the torrent naming guide for help on how to name your uploaded torrents properly. Use the Edition Information box on the upload page to denote different editions or versions of an album (e.g., censored version versus an uncensored version). If you need help merging or editing your upload, request it in this thread. For the album category/release type, follow the guidelines here.
          • +
        • ↑_ 2.3.4. Label your torrents according to site standards. Follow the torrent naming guide for help on how to name your uploaded torrents properly. Use the Edition Information box on the upload page to denote different editions or versions of an album (e.g., censored version versus an uncensored version). If you need help merging or editing your upload, please request help in this forum. For the album category/release type, follow the guidelines here.
        • ↑_ 2.3.5. Torrents should never have [REQ] or [REQUEST] in the title or artist name. If you fill a request using the Requests system, everyone who voted for it will be automatically notified.
          • -
        • ↑_ 2.3.6. 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. For detailed information on naming practices see this wiki and this wiki. Any descriptions like [Advance] or [CDM] (if you must use them) should be entered in the Edition Information box on the upload page, not in the title. Exceptions: If the album uses special capitalization, then you may follow that convention.
          • -
        • ↑_ 2.3.7. The Artist field in the torrent name should contain only the artist name. Do not add additional information about the artist in the artist field unless the album credits the artist in that manner. For example, "Artist X (of Band Y)" or "Band X (feat. Artist Y)." It is recommended that you search existing torrents for the artist name so that you can be sure that you name the artist the exact same way. A torrent with a proper artist name will be grouped with the existing torrents for that artist on a common artist page, and thus will be easy to find. Capitalization problems will also make a torrent trumpable. Labeling the artist incorrectly prevents your torrent from being grouped with the other torrents for the same artist. See this wiki for more information.
          • +
        • ↑_ 2.3.6. 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. For detailed information on naming practices see this wiki and this wiki. Any descriptions like [Advance] or [CDM] (if you must use them) should be entered in the Edition Information box on the upload page, not in the title. Exceptions: If the album uses special capitalization, then you may follow that convention.
          • +
        • ↑_ 2.3.7. The Artist field in the torrent name should contain only the artist name. Do not add additional information about the artist in the artist field unless the album credits the artist in that manner. For example, "Artist X (of Band Y)" or "Band X (feat. Artist Y)." It is recommended that you search existing torrents for the artist name so that you can be sure that you name the artist the exact same way. A torrent with a proper artist name will be grouped with the existing torrents for that artist on a common artist page, and thus will be easy to find. Capitalization problems will also make a torrent trumpable. Labeling the artist incorrectly prevents your torrent from being grouped with the other torrents for the same artist. See this wiki for more information.
        • ↑_ 2.3.8. The year of the original recording should be used for the upload page "Year" field. Use the recording year for "Year of the original release" (if you can establish it), and use the option to add the release year for the album or edition you are uploading in the Edition Information on the upload page. For example, all editions of The Beatles (White Album) would have 1968 in the main Year box. However, each of the various mono pressings, remasters, re-releases, expanded editions, reconstructions, etc. would have its respective release year in the Edition Information box.
        • ↑_ 2.3.9. All lossless analog rips should include clear information about source lineage. All lossless SACD digital layer analog rips and vinyl rips must include clear information about recording equipment used (see 2.8). If you used a USB turntable for a vinyl rip, clearly indicate this in your lineage information. Also include all intermediate steps up to lossless encoding, such as the program used for mastering, sound card used, etc. Lossless analog rips missing rip information can be trumped by better documented lossless analog rips of equal or better quality. In order to trump a lossless analog rip without a lineage, this lineage must be included as a .txt or .log file within the new torrent.
        • ↑_ 2.3.10. All lossless soundboard recordings must include clear information about source lineage. This information should be displayed in the torrent description. Optionally, the uploader may include the information in a .txt or .log file within the torrent. Lossless soundboard recordings missing lineage information will be deleted if reported (see 2.6.7).
          • @@ -335,16 +340,16 @@
        • ↑_ 2.3.13. Track numbers are required in file names (e.g., "01 - TrackName.mp3"). If a torrent without track numbers in the file names is uploaded, then a torrent with the track numbers in the file names can take its place. When formatted properly, file names will sort in order by track number or playing order. Also see 2.3.14. Exception: Track numbers are not required for single-track torrents.
        • ↑_ 2.3.14. When formatted properly, file names will alphabetically sort into the original playing order of the release.
            -
          • ↑_ 2.3.14.1.For albums with more than one artist, if the name of the artist is in the filename, it must come after the track number in order for the tracks to sort into the correct order. For example, "01 U2 - Where the Streets Have No Name.flac" is a properly formatted file name for a multiple-artist album. "U2 - 01 - Where the Streets Have No Name.mp3" is not correct in the context of a compilation album because the resultant file list will sort in alphabetical order by artist rather than by numerical track number. Note: there is no requirement for artist names to be in the track filenames, other than 2.3.16.2. Torrents that have improperly-formatted or incomplete file names will be trumpable.
            • +
          • ↑_ 2.3.14.1.For albums with more than one artist, if the name of the artist is in the filename, it must come after the track number in order for the tracks to sort into the correct order. For example, "01 U2 - Where the Streets Have No Name.flac" is a properly formatted file name for a multiple-artist album. "U2 - 01 - Where the Streets Have No Name.mp3" is not correct in the context of a compilation album because the resultant file list will sort in alphabetical order by artist rather than by numerical track number. Note: there is no requirement for artist names to be in the track filenames, other than 2.3.16.2. Torrents that have improperly-formatted or incomplete file names will be trumpable.
          • ↑_ 2.3.14.2.If a torrent has subfolders for multiple discs of a release, these subfolders must sort by disc order. If each disc has a title (torrents.php?id=62329, for example) and the discs are not numbered, this rule does not apply, and each subdirectory should have the disc name included.
        • ↑_ 2.3.15. 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. If you prefer to use one directory for all the audio files, you must use successive numbering. For example, Disc One has 15 tracks and Disc Two has 20. You may either number tracks in Disc One as #01-#15 and those of Disc Two as #16-#35 in the same directory, or you may add a Disc number before the track numbers such that the numbers are #1 06 for Disc One Track 06, and #2 03 for Disc 2 Track 03, and so forth.
        • ↑_ 2.3.16. Properly tag your music files.
            -
          • ↑_ 2.3.16.1.Certain meta tags (e.g., ID3, Vorbis) are required on all music uploads. Make sure to use the proper format tags for your files (e.g., no ID3 tags for FLAC - see 2.2.10.8. ID3v2 tags for files are highly recommended over ID3v1.
            • -
          • ↑_ 2.3.16.2.ID3 tags are recommended for AC3 torrents, but are not mandatory because the format does not natively support file metadata tagging (for AC3, the file names become the vehicle for correctly labeling media files). Because of this lack of support, the Album and Artist information must be included in the torrent folder for AC3 and DTS files. In addition, the Track Number and Track Title information must be included in the file names for AC3 and DTS files; for various artists compilations, the Track Artist must be included in the file names as well. ensuring that they also satisfy 2.3.14.
            • -
          • ↑_ 2.3.16.3.Torrents uploaded with both good ID3v1 tags and blank ID3v2 tags (a dual set of tags) are trumpable by torrents with either just good ID3v1 tags or good ID3v2 tags (a single set of tags). See this wiki for more information on ID3 tags.
            • +
          • ↑_ 2.3.16.1.Certain meta tags (e.g., ID3, Vorbis) are required on all music uploads. Make sure to use the proper format tags for your files (e.g., no ID3 tags for FLAC - see 2.2.10.8. ID3v2 tags for files are highly recommended over ID3v1.
            • +
          • ↑_ 2.3.16.2.ID3 tags are recommended for AC3 torrents, but are not mandatory because the format does not natively support file metadata tagging (for AC3, the file names become the vehicle for correctly labeling media files). Because of this lack of support, the Album and Artist information must be included in the torrent folder for AC3 and DTS files. In addition, the Track Number and Track Title information must be included in the file names for AC3 and DTS files; for various artists compilations, the Track Artist must be included in the file names as well. ensuring that they also satisfy 2.3.14.
            • +
          • ↑_ 2.3.16.3.Torrents uploaded with both good ID3v1 tags and blank ID3v2 tags (a dual set of tags) are trumpable by torrents with either just good ID3v1 tags or good ID3v2 tags (a single set of tags). See this wiki for more information on ID3 tags.
          • ↑_ 2.3.16.4.If you upload an album missing one or more of the required tags, then another user may add the tags, re-upload, and report your torrent for deletion. The required tags are:
            • Artist
              • @@ -356,8 +361,8 @@
            Note: The "Year" tag is optional, but strongly encouraged. However, if missing or incorrect, this is not grounds for trumping a torrent.
            • -
          • ↑_ 2.3.17. The torrent artist for classical works should use the full composer name. Before uploading see this wiki for guidelines on uploading classical music torrents. Also, consult this wiki for a full explanation of the classical music tagging system.
            • -
          • ↑_ 2.3.18. 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, fixing slight misspellings, or missing an alternate spelling of an artist (e.g., excluding "The" before a band name) are insufficient grounds for replacing other torrents. Artist names that are misspelled in the tags are grounds for trumping; this includes character accents and characters that mean one letter in one language and a different letter in another language. Improper capitalization in the tags is grounds for trumping; this includes artist tags (or composer tags) that contain names that are all capitalized or track titles that are all capitalized. Tags with multiple entries in the same tag (e.g., track number and track title in the track title tags; or track number, artist, and track title in the artist tags) are subject to trumping. You may trump a release if the tags do not follow the data from a reputable music cataloguing service such as Musicbrainz or Discogs. In the case of a conflict between reputable listings, either tagged version is equally preferred on the site and cannot trump the other. For example, an album is tagged differently in Musicbrainz and in Discogs. Either style of tagging is permitted; neither is "better" than the other. In that case, any newly tagged torrents replacing an already properly tagged torrent, which follows good tagging convention, will result in a dupe. Note: For classical music, please follow these tagging guidelines.
            • +
          • ↑_ 2.3.17. The torrent artist for classical works should use the full composer name. Before uploading see this wiki for guidelines on uploading classical music torrents. Also, consult this wiki for a full explanation of the classical music tagging system.
            • +
          • ↑_ 2.3.18. 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, fixing slight misspellings, or missing an alternate spelling of an artist (e.g., excluding "The" before a band name) are insufficient grounds for replacing other torrents. Artist names that are misspelled in the tags are grounds for trumping; this includes character accents and characters that mean one letter in one language and a different letter in another language. Improper capitalization in the tags is grounds for trumping; this includes artist tags (or composer tags) that contain names that are all capitalized or track titles that are all capitalized. Tags with multiple entries in the same tag (e.g., track number and track title in the track title tags; or track number, artist, and track title in the artist tags) are subject to trumping. You may trump a release if the tags do not follow the data from a reputable music cataloguing service such as Musicbrainz or Discogs. In the case of a conflict between reputable listings, either tagged version is equally preferred on the site and cannot trump the other. For example, an album is tagged differently in Musicbrainz and in Discogs. Either style of tagging is permitted; neither is "better" than the other. In that case, any newly tagged torrents replacing an already properly tagged torrent, which follows good tagging convention, will result in a dupe. Note: For classical music, please follow these tagging guidelines.
          • ↑_ 2.3.19. Avoid embedding large images if including cover art in the meta tags. Do not embed large images (in excess of 512 KB) in the file meta tags. It adds unnecessary bloat to the files. Include the artwork in a separate directory if it is too big or if it consists of high-resolution images. Should you include an image of over 512 KB as embedded artwork, your torrent will be trumpable.
    @@ -378,8 +383,8 @@