|
|
|
|
@ -185,7 +185,7 @@
|
|
|
|
|
</li>
|
|
|
|
|
<li id="r2.1.20"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.20">2.1.20.</a> <strong>User made discographies may not be uploaded.</strong> 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.</li>
|
|
|
|
|
<li id="r2.1.21"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.21">2.1.21.</a> <strong><a href="wiki.php?action=article&id=386">Pre-emphasis</a> is allowed in lossless torrents only.</strong> 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.</li>
|
|
|
|
|
<li id="r2.1.22"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.22">2.1.22.</a> <strong>Edition Information must be provided for digitally-sourced torrents.</strong> 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 <a href="wiki.php?action=article&id=367">this wiki</a> for more information on album editions.</li>
|
|
|
|
|
<li id="r2.1.22"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.22">2.1.22.</a> <strong>Edition Information must be provided for digitally-sourced torrents.</strong> 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 <a href="wiki.php?action=article&id=367">this wiki</a> for more information on album editions.</li>
|
|
|
|
|
<li id="r2.1.23"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.23">2.1.23.</a> <strong>Audio can only be ripped from a video game CD under very specific circumstances. Audio ripped from a video game DVD is not allowed on site.</strong>
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r2.1.23.1"><a href="#r2.1.23"><strong>↑_</strong></a> <a href="#r2.1.23.1">2.1.23.1.</a> <strong>This audio layer must comply with the Red Book standard for audio data.</strong> If there is no Red Book 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 <a href="wiki.php?action=article&id=953">this wiki</a> for information about providing proof).</li>
|
|
|
|
|
@ -253,11 +253,11 @@
|
|
|
|
|
</li>
|
|
|
|
|
<li id="r2.2.10.7"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.7">2.2.10.7.</a> <strong>A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet.</strong> See <a href="wiki.php?action=article&id=168">this wiki</a> for more information on cue sheets.
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r2.2.10.7.1"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.1">2.2.10.7.1.</a> <strong>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 <a href="wiki.php?action=article&id=386">pre-emphasis</a> flags.</strong> 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.</li>
|
|
|
|
|
<li id="r2.2.10.7.1"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.1">2.2.10.7.1.</a> <strong>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 <a href="wiki.php?action=article&id=386">pre-emphasis</a> flags.</strong> 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.</li>
|
|
|
|
|
<li id="r2.2.10.7.2"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.2">2.2.10.7.2.</a> <strong>Exceptions: An <a href="http://www.exactaudiocopy.de/" target="_blank">EAC</a> 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.</strong> </li>
|
|
|
|
|
</ul>
|
|
|
|
|
</li>
|
|
|
|
|
<li id="r2.2.10.8"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.8">2.2.10.8.</a> <strong>FLAC rips that contain ID3 tags or other non-compliant tags for FLAC may be trumped by rips with identical scores that have the faulty tags removed and replaced with the standard for each format.</strong> Enabling ID3 tags in <a href="http://www.exactaudiocopy.de/" target="_blank">EAC</a> when ripping to FLAC may prevent some players from playing the files because of the inclusion of ID3 headers. If you wish to trump a FLAC rip that was ripped with ID3 tags enabled, upload the corrected torrent with the proper Vorbis comments and report the old torrent. Add information about your tag clean-up in the "Release description", or your torrent may be deleted as a dupe. Do not edit the log and change the ID3 tag setting to "No." Note: A simple way of getting rid of the ID3 header is to decompress the files to WAV, then compressing the files to FLAC, and adding the proper Vorbis comments.</li>
|
|
|
|
|
<li id="r2.2.10.8"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.8">2.2.10.8.</a> <strong>FLAC rips that contain ID3 tags or other non-compliant tags for FLAC may be trumped by rips with identical scores that have the faulty tags removed and replaced with the standard for each format.</strong> Enabling ID3 tags in <a href="http://www.exactaudiocopy.de/" target="_blank">EAC</a> when ripping to FLAC may prevent some players from playing the files because of the inclusion of ID3 headers. If you wish to trump a FLAC rip that was ripped with ID3 tags enabled, upload the corrected torrent with the proper Vorbis comments and report the old torrent. Add information about your tag clean-up in the "Release description", or your torrent may be deleted as a dupe. Do not edit the log and change the ID3 tag setting to "No". Note: A simple way of getting rid of the ID3 header is to decompress the files to WAV, then compressing the files to FLAC, and adding the proper Vorbis comments.</li>
|
|
|
|
|
<li id="r2.2.10.9"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.9">2.2.10.9.</a> <strong>No log editing is permitted.</strong>
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r2.2.10.9.1"><a href="#r2.2.10.9"><strong>↑_</strong></a> <a href="#r2.2.10.9.1">2.2.10.9.1.</a> <strong>Forging log data is a serious misrepresentation of quality, and will result in a warning and the loss of your uploading privileges when the edited log is found.</strong> We recommend that you do not open the rip log file for any reason. However, if you must open the rip log, do not edit anything in the file for any reason. If you discover that one of your software settings is incorrect in the ripping software preferences, you must rip the CD again with the proper settings. Do not consolidate logs under any circumstances. If you must re-rip specific tracks or an entire disc and the rip results happen to have the new log appended to the original, leave them as is. Do not remove any part of either log, and never copy/paste parts of a new log over an old log.</li>
|
|
|
|
|
@ -291,17 +291,17 @@
|
|
|
|
|
<h5 id="h2.3"><a href="#h2.3k"><strong>↑</strong></a> <a href="#h2.3">2.3.</a> Formatting</h5>
|
|
|
|
|
<div class="box pad" style="padding: 10px 10px 10px 20px;">
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r2.3.1"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.1">2.3.1.</a> <strong>Music releases must be in a directory that contains the music.</strong> 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."</li>
|
|
|
|
|
<li id="r2.3.2"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.2">2.3.2.</a> <strong>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.</strong> 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.</li>
|
|
|
|
|
<li id="r2.3.1"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.1">2.3.1.</a> <strong>Music releases must be in a directory that contains the music.</strong> 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".</li>
|
|
|
|
|
<li id="r2.3.2"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.2">2.3.2.</a> <strong>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.</strong> 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.</li>
|
|
|
|
|
<li id="r2.3.3"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.3">2.3.3.</a> <strong>Avoid creating unnecessary nested folders (such as an extra folder for the actual album) inside your properly named directory.</strong> 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, e.g., the main torrent folder is "<samp>Adele - 19 (2008) - FLAC</samp>" while appropriate sub-folders may include "<samp>19 (Disc 1of2)</samp>" or "<samp>19</samp>" and "<samp>Live From The Hotel Cafe (Disc 2of2)</samp>" or "<samp>Acoustic Set Live From The Hotel Cafe, Los Angeles</samp>". 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.</li>
|
|
|
|
|
<li id="r2.3.4"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.4">2.3.4.</a> <strong>Label your torrents according to site standards.</strong> Follow the <a href="wiki.php?action=article&id=159">torrent naming guide</a> for help on how to name your uploaded torrents properly. Use the Edition Information box on the <a href="upload.php">upload page</a> 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 <a href="forums.php?action=viewforum&forumid=61">this forum</a>. For the album category/release type, follow the <a href="wiki.php?action=article&id=202">guidelines here</a>.</li>
|
|
|
|
|
<li id="r2.3.5"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.5">2.3.5.</a> <strong>Torrents should never have [REQ] or [REQUEST] in the title or artist name.</strong> If you fill a request using the <a href="requests.php">Requests system</a>, everyone who voted for it will be automatically notified.</li>
|
|
|
|
|
<li id="r2.3.6"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.6">2.3.6.</a> <strong>Torrent album titles must accurately reflect the actual album titles.</strong> 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 <a href="wiki.php?action=article&id=369">this wiki</a> and <a href="wiki.php?action=article&id=317">this wiki</a>. Any descriptions like [Advance] or [CDM] (if you must use them) should be entered in the Edition Information box on the <a href="upload.php">upload page</a>, not in the title. Exceptions: If the album uses special capitalization, then you may follow that convention.</li>
|
|
|
|
|
<li id="r2.3.7"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.7">2.3.7.</a> <strong>The Artist field in the torrent name should contain only the artist name.</strong> 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 <a href="wiki.php?action=article&id=369">this wiki</a> for more information.</li>
|
|
|
|
|
<li id="r2.3.7"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.7">2.3.7.</a> <strong>The Artist field in the torrent name should contain only the artist name.</strong> 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 <a href="wiki.php?action=article&id=369">this wiki</a> for more information.</li>
|
|
|
|
|
<li id="r2.3.8"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.8">2.3.8.</a> <strong>The year of the original recording should be used for the <a href="upload.php">upload page</a> "Year" field.</strong> 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 <a href="upload.php">upload page</a>. 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.</li>
|
|
|
|
|
<li id="r2.3.9"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.9">2.3.9.</a> <strong>All lossless analog rips should include clear information about source lineage.</strong> All lossless SACD digital layer analog rips and vinyl rips must include clear information about recording equipment used (see <a href="#h2.8">2.8</a>). 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.</li>
|
|
|
|
|
<li id="r2.3.10"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.10">2.3.10.</a> <strong>All lossless soundboard recordings must include clear information about source lineage.</strong> 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 <a href="#r2.6.7">2.6.7</a>).</li>
|
|
|
|
|
<li id="r2.3.11"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.11">2.3.11.</a> <strong>File names must accurately reflect the song titles.</strong> You may not have file names like <samp>01track.mp3</samp>, <samp>02track.mp3</samp>, etc. Torrents containing files that are named with incorrect song titles can be trumped by properly labeled torrents. Also, torrents that are sourced from the scene but do not have the Scene label must comply with site naming rules (no release group names in the file names, no advertisements in the file names, etc.). Note that these must be substantial improvements such as the removal of garbage characters. Small changes such as diacritical marks are insufficient grounds for trumping. English translations of song titles in file names are encouraged but not necessary for foreign language song titles. If all the letters in the track titles are capitalized, the torrent is trumpable. Exceptions: Rare albums featuring no track listing or untitled tracks may have file names like <samp>01track.mp3</samp>, <samp>02track.mp3</samp>, and so forth. Please note this track list in the "Album description." If foreign language characters create playback problems for some systems and cannot be coherently translated, file names such as "<samp>01track</samp>" are acceptable for those few cases.</li>
|
|
|
|
|
<li id="r2.3.11"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.11">2.3.11.</a> <strong>File names must accurately reflect the song titles.</strong> You may not have file names like <samp>01track.mp3</samp>, <samp>02track.mp3</samp>, etc. Torrents containing files that are named with incorrect song titles can be trumped by properly labeled torrents. Also, torrents that are sourced from the scene but do not have the Scene label must comply with site naming rules (no release group names in the file names, no advertisements in the file names, etc.). Note that these must be substantial improvements such as the removal of garbage characters. Small changes such as diacritical marks are insufficient grounds for trumping. English translations of song titles in file names are encouraged but not necessary for foreign language song titles. If all the letters in the track titles are capitalized, the torrent is trumpable. Exceptions: Rare albums featuring no track listing or untitled tracks may have file names like <samp>01track.mp3</samp>, <samp>02track.mp3</samp>, and so forth. Please note this track list in the "Album description". If foreign language characters create playback problems for some systems and cannot be coherently translated, file names such as "<samp>01track</samp>" are acceptable for those few cases.</li>
|
|
|
|
|
<li id="r2.3.12"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.12">2.3.12.</a> <strong>The maximum character length for files is 180 characters.</strong> Path length values must not be so long that they cause incompatibility problems with operating systems and media players. For example, "<samp>My Artist Name - My Album Name (2012) - FLAC/01 - Long Track Name for the First Track.flac</samp>" is a typical torrent folder that contains the audio files. This path name consists of 90 characters. As of September 01, 2012, new torrents will be trumpable if their path lengths exceed 180 characters. This limit includes the number of characters in the main torrent folder (in this case, 46 characters), any sub-folders, and files within that torrent folder. For example, unnecessarily nested folders will count towards this limit; lengthy classical music file names will count towards this limit. Torrents that were uploaded prior to September 01, 2012 with character lengths that are longer than 180 characters may remain on the site. However, torrents with exceedingly long path lengths will only remain on the site at the discretion of staff.</li>
|
|
|
|
|
<li id="r2.3.13"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.13">2.3.13.</a> <strong>Track numbers are required in file names (e.g., "<samp>01 - TrackName.mp3</samp>").</strong> 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 <a href="#r2.3.14">2.3.14</a>. Exception: Track numbers are not required for single-track torrents.</li>
|
|
|
|
|
<li id="r2.3.14"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.14">2.3.14.</a> <strong>When formatted properly, file names will alphabetically sort into the original playing order of the release.</strong>
|
|
|
|
|
@ -329,7 +329,7 @@
|
|
|
|
|
</li>
|
|
|
|
|
<li id="r2.3.17"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.17">2.3.17.</a> <strong>The torrent artist for classical works should use the full composer name.</strong> Before uploading see <a href="wiki.php?action=article&id=700">this wiki</a> for guidelines on uploading classical music torrents. Also, consult <a href="wiki.php?action=article&id=691">this wiki</a> for a full explanation of the classical music tagging system.</li>
|
|
|
|
|
<li id="r2.3.18"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.18">2.3.18.</a> <strong>Newly re-tagged torrents trumping badly tagged torrents must reflect a substantial improvement over the previous tags.</strong> 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 <a href="https://musicbrainz.org/" target="_blank">MusicBrainz</a> or <a href="http://www.discogs.com/" target="_blank">Discogs</a>. 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 <a href="https://musicbrainz.org/" target="_blank">MusicBrainz</a> and in <a href="http://www.discogs.com/" target="_blank">Discogs</a>. 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 <a href="wiki.php?action=article&id=691">tagging guidelines</a>.</li>
|
|
|
|
|
<li id="r2.3.19"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.19">2.3.19.</a> <strong>Avoid embedding large images if including cover art in the meta tags.</strong> 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.</li>
|
|
|
|
|
<li id="r2.3.19"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.19">2.3.19.</a> <strong>Avoid embedding large images if including cover art in the meta tags.</strong> 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. When attempting to remove embedded images, make sure that the padding is removed as well. Refer to <a href="wiki.php?action=article&id=1206">this wiki article</a> for more information.</li>
|
|
|
|
|
<li id="r2.3.20"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.20">2.3.20.</a> <strong>Leading spaces are not allowed in any file or folder names.</strong> Leading spaces cause usability and interoperability problems among various operating systems and programs. Torrents with file or folder names that contain leading space characters are trumpable.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</div>
|
|
|
|
|
@ -477,7 +477,7 @@
|
|
|
|
|
<li id="r2.9.3"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.3">2.9.3.</a> <strong> Blu-ray rip sources must be properly labeled.</strong>
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r2.9.3.1"><a href="#r2.9.3"><strong>↑_</strong></a> <a href="#r2.9.3.1">2.9.3.1.</a> <strong> If the source was lossy (e.g., AC3 or DTS) do not transcode to other formats.</strong> </li>
|
|
|
|
|
<li id="r2.9.3.2"><a href="#r2.9.3"><strong>↑_</strong></a> <a href="#r2.9.3.2">2.9.3.2.</a> <strong> If the source was a genuine lossless track, identify the track in the album edition field, e.g., "16-bit PCM" or "24-bit DTS-HD MA 5.1."</strong> Sampling rate information may also be included (e.g., "16/48 LPCM") in the album edition field. </li>
|
|
|
|
|
<li id="r2.9.3.2"><a href="#r2.9.3"><strong>↑_</strong></a> <a href="#r2.9.3.2">2.9.3.2.</a> <strong> If the source was a genuine lossless track, identify the track in the album edition field, e.g., "16-bit PCM" or "24-bit DTS-HD MA 5.1".</strong> Sampling rate information may also be included (e.g., "16/48 LPCM") in the album edition field. </li>
|
|
|
|
|
</ul>
|
|
|
|
|
</li>
|
|
|
|
|
<li id="r2.9.4"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.4">2.9.4.</a> <strong>Lineage information for a Blu-ray transfer is required and should be included in the torrent folder.</strong>
|
|
|
|
|
@ -559,7 +559,7 @@
|
|
|
|
|
<li id="r4.1.2"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.2">4.1.2.</a> <strong>All applications must come with a crack, keygen, or other method of ensuring that downloaders can install them easily.</strong> App torrents with keygens, cracks, or patches that do not work or torrents missing clear installation instructions will be deleted if reported. No exceptions.</li>
|
|
|
|
|
<li id="r4.1.3"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.3">4.1.3.</a> <strong>App releases must not be freely available tools.</strong> Application releases cannot be freely downloaded anywhere from any official source. Nor may you upload open source applications where the source code is available for free. Closed or shareware installers like Crossover Office are allowed. Note: If all official sources stop hosting and remove a freely available application and its source code from their site(s) due to varying reasons (e.g., legal concerns, dead development, etc.), the application ceases to be freely available. You may then upload it in that case.</li>
|
|
|
|
|
<li id="r4.1.4"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.4">4.1.4.</a> <strong>Release descriptions for applications must contain good information about the application.</strong> You should either have a small description of the program (either taken from its web site or from an NFO file) or a link to the information — but ideally both. Torrents missing this information will be deleted when reported.</li>
|
|
|
|
|
<li id="r4.1.5"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.5">4.1.5.</a> <strong>The torrent title must have a descriptive name.</strong> The torrent title should at least include the application name and release version. Optionally, you may include additional labels for operating system and method of circumvention (e.g., crack, patch, keygen, or serial). For example, "AcrylicApps Wallet v3.0.1.493 MacOSX Cracked."</li>
|
|
|
|
|
<li id="r4.1.5"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.5">4.1.5.</a> <strong>The torrent title must have a descriptive name.</strong> The torrent title should at least include the application name and release version. Optionally, you may include additional labels for operating system and method of circumvention (e.g., crack, patch, keygen, or serial). For example, "AcrylicApps Wallet v3.0.1.493 MacOSX Cracked".</li>
|
|
|
|
|
<li id="r4.1.6"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.6">4.1.6.</a> <strong>Use relevant tags for your torrent.</strong> Add all applicable default <a href="?p=tag">Gazelle tags</a> to help downloaders find your torrent. The default tags are apps.mac for Mac applications, apps.windows for Windows applications, and apps.sound for audio applications. You may add additional tags if the default ones do not apply (such as apps.linux).</li>
|
|
|
|
|
<li id="r4.1.7"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.7">4.1.7.</a> <strong>Games of any kind are prohibited (see <a href="#r1.2.5">1.2.5</a>).</strong> </li>
|
|
|
|
|
<li id="r4.1.8"><a href="#h4.1"><strong>↑_</strong></a> <a href="#r4.1.8">4.1.8.</a> <strong>Application "packs" are not allowed.</strong> That means no 0-day packs or "video utilities" compilations. Also, packaging multiple versions of the same application into a single torrent is not allowed (e.g., Adobe Acrobat 8 and Adobe Acrobat 9 in a single torrent). Exceptions: The applications are from the same company and an official release. For example, Adobe CS and Macromedia Studio packaged in one set.</li>
|
|
|
|
|
@ -605,8 +605,8 @@
|
|
|
|
|
<ul>
|
|
|
|
|
<li id="r5.2.1"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.1">5.2.1.</a> <strong>Multi-comic and series packs must follow site formatting requirements.</strong> Multi-comic and series packs are both accepted and encouraged but care must be taken to make a valid compilation. The rules in this section outline the requirements for multi-comic torrents.</li>
|
|
|
|
|
<li id="r5.2.2"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.2">5.2.2.</a> <strong>0-Day comic packs are allowed.</strong> Make sure such uploads are synchronized with any previous packs. 0-Day comic uploads must not be missing any of their corresponding DCP or Minutemen scans for that time period.</li>
|
|
|
|
|
<li id="r5.2.3"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.3">5.2.3.</a> <strong>Collections may not span more than one comic title.</strong> You may not include multiple, different comic titles in a single collection, e.g., "The Amazing Spider-Man #1" and "The Incredible Hulk #1." Exceptions: Titles may contain more than one comic title if either of the following is true: it's a recognized comic crossover/event or it's a DCP weekly release.</li>
|
|
|
|
|
<li id="r5.2.4"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.4">5.2.4.</a> <strong>Any "multi-part" comic enveloping the whole event is allowed as a single torrent.</strong> Whole events may be uploaded together. For example, the comics "<samp>Buffy the Vampire Slayer Season Eight - 2007 - part 1.cbr</samp>" and "<samp>Buffy the Vampire Slayer Season Eight - 2007 - The Long Way Home Part 2.cbr</samp>" can be uploaded as a single torrent provided there are only 2 parts to "The Long Way Home."</li>
|
|
|
|
|
<li id="r5.2.3"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.3">5.2.3.</a> <strong>Collections may not span more than one comic title.</strong> You may not include multiple, different comic titles in a single collection, e.g., "The Amazing Spider-Man #1" and "The Incredible Hulk #1". Exceptions: Titles may contain more than one comic title if either of the following is true: it's a recognized comic crossover/event or it's a DCP weekly release.</li>
|
|
|
|
|
<li id="r5.2.4"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.4">5.2.4.</a> <strong>Any "multi-part" comic enveloping the whole event is allowed as a single torrent.</strong> Whole events may be uploaded together. For example, the comics "<samp>Buffy the Vampire Slayer Season Eight - 2007 - part 1.cbr</samp>" and "<samp>Buffy the Vampire Slayer Season Eight - 2007 - The Long Way Home Part 2.cbr</samp>" can be uploaded as a single torrent provided there are only 2 parts to "The Long Way Home".</li>
|
|
|
|
|
<li id="r5.2.5"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.5">5.2.5.</a> <strong>Torrents containing complete volumes of comics may be uploaded.</strong> For example, "The Amazing Spider-Man Vol. 1 #1-#441" can be uploaded.</li>
|
|
|
|
|
<li id="r5.2.6"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.6">5.2.6.</a> <strong>Torrents spanning multiple volumes are too large and must be uploaded as separate volumes.</strong> </li>
|
|
|
|
|
<li id="r5.2.7"><a href="#h5.2"><strong>↑_</strong></a> <a href="#r5.2.7">5.2.7.</a> <strong>Torrents containing specific #Number-#CurrentDay issues are allowed only if the comics appear in no other pack.</strong> For example, if #1-#35 are already on the site and the current issue is #50, #1-#50 is NOT allowed to be uploaded, but #36-#50 is allowed.</li>
|
|
|
|
|
|
Git