BioTorrents.de’s version of Gazelle
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

requests.php 3.4KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. <?php
  2. View::show_header('Request rules');
  3. ?>
  4. <div>
  5. <div class="header">
  6. <h2>
  7. Request rules
  8. </h2>
  9. </div>
  10. <div class="box pad rule_summary">
  11. <ul>
  12. <li>
  13. <strong>Uploads fulfilling a request must actually meet the request requirements.</strong>
  14. It doesn't matter if you think your upload is better than what was requested, or even if the requested content
  15. doesn't exist and the request is unfillable.
  16. You may not fill a request with any upload that does not meet all of the given request criteria.
  17. If you feel that the requester made a mistake, contact them and get them to change the request before you try to
  18. fill it.
  19. </li>
  20. <li>
  21. <strong>Do not make requests for torrents that break the rules.</strong>
  22. It is your responsibility that the request follows the rules.
  23. Your request will be deleted, and you will not get your bounty back.
  24. Requests cannot be more specific than the upload (and trumping) rules.
  25. </li>
  26. <li>
  27. <strong>Put format specifics in the request description.</strong>
  28. If you're requesting a particular platform, file format, etc., put that information in the request description.
  29. Do not put it in the title of the request.
  30. </li>
  31. <li>
  32. <strong>Only one torrent per request.</strong>
  33. No requests for multiple data or vague requirements.
  34. You may ask for any of several formats, but you cannot demand all of them.
  35. For example, you may ask for either a FASTA or a GenBank, but not both formats.
  36. </li>
  37. <li>
  38. <strong>When uploading to fill a request, use the [Upload request] link on the request's page.</strong>
  39. This will autofill some of the metadata for the torrent, such as title and artist.
  40. This prevents some errors that may cause your upload to break the rules, have your request unfilled, have your
  41. bounty removed, and possibly cause you to receive a warning.
  42. </li>
  43. <li>
  44. <strong>Do not unfill requests for trivial reasons.</strong>
  45. If you did not specify in your request what you wanted, it's your fault.
  46. Do not unfill and later change the description.
  47. Do not unfill requests if you are unsure of what you are doing.
  48. Ask for help from <a href="/staff.php">first-line support or staff</a> in that case.
  49. You may only unfill the request if the torrent does not fit your specifications stated clearly in the request.
  50. </li>
  51. <li>
  52. <strong>All users must have an equal chance to fill a request.</strong>
  53. Exchanging favors for other users is probably fine, but abusing the request system is not tolerated.
  54. That includes making specific requests for certain users (whether explicitly named or not).
  55. Making requests and then unfilling so that one particular user can fill the request is not allowed.
  56. If reported, both the requester and user filling the request will receive a warning and lose the request bounty.
  57. </li>
  58. <li>
  59. <strong>No manipulation of the requester for bounty.</strong>
  60. The bounty is a reward for helping other users.
  61. It should not be a ransom.
  62. Any user who openly refuses to fill a request unless the bounty is increased will face harsh punishment if
  63. they're being a shithead about it.
  64. </li>
  65. </ul>
  66. </div>
  67. <?php include('jump.php'); ?>
  68. </div>
  69. <?php View::show_footer();