fserv.html

黑客培训教程

  One syntax note: when a word appears between <these> , then that means 
  you fill the space basically. So if the tutorial says " get <filename> 
  " Then you should replace filename with the appropriate word (So if you 
  wanted picture.jpg then you'd type get picture.jpg). And to keep this 'beginner 
  friendly' I chose only the bare-bones commands. Please continue.<br>
  <br>
</p>
<table width="50%" border="0" cellspacing="2" cellpadding="2">
  <tr> 
    <td><b>Command</b></td>
    <td><b>What it Does - Example</b></td>
  </tr>
  <tr> 
    <td>DIR/LS</td>
    <td>Lists files - N/A </td>
  </tr>
  <tr> 
    <td>GET</td>
    <td>gets files - get &lt;filename&gt;</td>
  </tr>
  <tr> 
    <td>CD</td>
    <td>Changes Directory - cd &lt;foldername&gt;</td>
  </tr>
  <tr> 
    <td>CD ..</td>
    <td>Goes up a directory - cd ..</td>
  </tr>
</table>
<p>Now to understand what the user/host's computer connection is, I'm going to 
  have to explain a little bit of the fserv setup process. Now, when someone (the 
  host) sets up an fserv, they edit and configure the script, which is just basiclally 
  changing options. And one of those options is a ROOT DIRECTORY. The root directory 
  is the first directory. So if his root directory is C:/Folder/First/ Then the 
  first directory you're in when you get on his fserv is C:/Folder/First/ . So 
  when you are changing directories and such, then you are changing directories 
  on his machine. So basically, the script is just letting you know what's available 
  (what folders you have accesst to) and let's you make your decisions on what 
  files to get. You see, there is no real server involved. All it is is a script 
  which acts like one by accpting commands and sending and getting files. Now 
  on to sending and getting.<br>
  <br>
  <b><a name="9"></a>C. Uploading and Downloading Information</b><br>
  <br>
  <b><a name="10"></a>1. The Credit System</b><br>
  <br>
  The Credit System is one of the largest and most intriguing aspects of fserving. 
  It really is one of the few things, besides just plain generosity, that would 
  make someone want to become a host. But what is it about? Well let's suppose 
  you get on a fserv that deals with mp3s (for legalities sake, let's say 'legal' 
  mp3s). Ok, so the guy who hosts the thing doesn't just want to give out mp3s, 
  I mean why would he? It's simply human nature to want something in return. So 
  that's where the Credit System comes in. You see, if the guy's fserv script 
  uses the Credit System, then he can 'charge' for the mp3s. And I don't mean 
  money, I mean, well, credit. You see, here's how it works. There are three kinds 
  of fservs, all of which have some sort of Credit System (I'll get into each 
  one in detail later). Now, with the Credit System, the hosts sets 2 things: 
  STARTING CREDIT and RATIO. Both of these are very important to how your fserv 
  experience goes (and which fservs you use). Ok, lets start with Starting Credit. 
  Starting Credit, is simply, how much Credit you start with. Much like how much 
  money you start with in a game of Monopoly. Now remember, all values are in 
  BYTES, not KILOBYTES. So if the Starting Credit is 1000000 , then you start 
  with a MEGABYTE worth of credit. So what is Credit for, you ask. Well, if you 
  want a mp3 thats 3 megs, then you need 3 megs of Credit (which is 3000000 in 
  byte/credits form). So how do you get that credit? Uploading, which I'll get 
  into later. Now lets get into Ratio, which is just as important as Starting 
  Credit, if not more. Now what Ratio is, is a way for a hosts to allow more credit 
  to be given to uploaders. Why this was even thought of in the first place is 
  not even known, but it's still implemented in almost every script. Now, ratio 
  is represented by the same means as in Mathematics, with 2 numbers seperated 
  by a colon (2:3). Now how it works out in lamens terms is different. Ok, this 
  can be confusing. If a fserv has a 1:2 ratio, than that basically means for 
  every byte that I upload I get 2 bytes back. So, if I upload a 500k picture 
  (equal to 500000 bytes/credits) to a this fserv, then I get 1 meg of credit 
  back (equal to 1000000 bytes/credits). The same works for different ratios such 
  as 1:4. Except, in this case for every byte uploaded, you get 4 bytes back, 
  and so on. Now, what about LEECH? If you've been to the fserving channels before, 
  you've heard that term tossed around. Well, it's actually simple. Let's suppose 
  your on a Mp3 fserv, and it says in his RULES MESSAGE that he'll give Leech 
  for an Mp3 of a certain song. So you know that you've got it, so you upload 
  it. Then he'll give you Leech, which means you have infinite Credits. Basically, 
  Leech is like being able to have anything in a store for free. There are also 
  LEECH FSERVS, which I'll get into later. <br>
  <br>
  <b><a name="11"></a>2. Uploading </b><br>
  <br>
  Now here's a topic that evaded me for a long time. First of all, you should 
  know by now what you upload for (Answer: Credit), and what happens when you 
  upload (The file gets sent to the hosts computer). But how do you upload? Well, 
  it's actually very simple. If the script takes the hosts place, but pretty much 
  does the same things, then if you wanted to upload to the fserv, then all you 
  have to do is do a DCC Send to the fserv! It's that simple. And after your file 
  is done sending, then you get your credit. Always in that order. Now, there 
  is some ethics and manners involved with this, but I'll get into that in a bit.<br>
  <br>
  <b><a name="12"></a>3. Downloading </b><br>
  <br>
  Also a very simple topic. Ok, basically, you get a file by using the command 
  &quot;get &lt;filename&gt;&quot; (without the quotes). But first, you must have 
  enough Credit. Which you do by uploading, of course. So this is a simpler subject 
  and the very essense of fserving. Now, there is a limit to how much you download 
  at a time. It depends on the fserv though. This will be discussed when I teach 
  about hosting your own fserv later on in the tutorial.<br>
  <br>
  <b><a name="13"></a>D. Information on the Types of Scripts</b><br>
  <br>
  <b><a name="14"></a>1. Byte Ratio Scripts</b><br>
  <br>
  The most popular of the Scripts simply because the host is guaranteed something 
  in return. Very simple, because it uses the exact Credit System I described 
  above. Where the Ratio describes bytes sent:bytes returned. This is the Script 
  type of choice for Mp3, Video, Porn, etc. hosts. As said before, this type Script 
  is used anytime that the host wants something in return for supplying everyone 
  with these files. Thus, it is claimed as the King of Scripts.<br>
  <br>
  <b><a name="15"></a>2. File Ratio Scripts</b><br>
  <br>
  A very bizarre type of Script. Not many people use it anymore because of the 
  high potential of 'rip-offs'. It uses the same Credit System with the exception 
  that instead of the Ratio being bytes sent:bytes returned , it's files sent:files 
  returned. So you can easily see what the potential for getting 'ripped' is. 
  For example, let's use that mp3 fserv again. So, this mp3 fserv is using a File 
  Ratio Script with a 1:3 ratio. So after someone uploads a file (yeah, any file) 
  then he then gets permission to download 3 files. Yeah, bytes/credit has nothing 
  to do with anything. The problem is that I could upload 2k picture and then 
  get 3 files for basically nothing. These are rare these days, but I suppose, 
  are still used in trusted enviornments - Private Channels where only trusted 
  people are given access. Though in most other cases, these aren't used that 
  often. Surprisingly Leech Scripts are way more common.<br>
  <br>
  <b><a name="16"></a>3. Leech Scripts</b><br>
  <br>
  These are surprisingly popular, though not as popular as the Byte Ratio Scripts. 
  These are just as they say, completely Leeched to everyone. So there are no 
  Ratios, no Uploading, no Starting Credits, and definately no ways of getting 
  Leech (I mean you already have it!). These also usually come with another feature, 
  not often found on other types of Scripts, QUEUES. Very simply, Queueing is 
  a way that you can send out minimal files while still giving them all they need. 
  Basically a Queue is a 'slot' that, once the maximum amount of simultaneous 
  sends has been met, will hold the file 'til a slot opens up, then send it. So 
  if a fserv only allows 2 Simulataneous downloads and there's 2 files being sent, 
  and I try to get a file, the script will put it in a Queue Slot, which then 
  will send it when one of the sends are done. So it basically holds it until 
  it can send it. If you don't understand, you will when you use one. It's still 
  a very nice feature. These Scripts are usually found in any fservs that deal 
  with smaller files like Text Files (*.txt). They're also found in fservs that 
  deal with emulation and any type of fserv where the host doesn't want anything 
  in return.<br>
  <br>
  <font size="4"><b><a name="17"></a>III. PREVENTION OF GETTING BANNED</b></font><br>
  <br>
  <b><a name="18"></a>A. Proper Fserv Manners</b><br>
  <br>
  You will soon learn that there is no worse feeling than being banned. As an 
  experienced user and host, I understand both sides. But unfortunately, the user 
  must follow the host's rules. And that's really understandable cosidering that 
  hosting a fserv is a service and a major pain in the ass sometimes, so the user 
  really isn't a priority. And that's why most hosts don't even pay attention 
  to their fservs, cause they don't wanna deal with the users (Though I don't 
  like that fact). So, as a user, if you don't follow the rules you will be kicked/banned 
  so you need to learn some fserv ethics which will help you in the future. Hell, 
  if you follow, you may not be banned ever again.<br>
  <br>
  <b><a name="19"></a>B. Staying on a Host's Good Side</b></p>
<p> Now I don't wanna come off as saying that you've gotta kiss the host's ass. 
  That's not it at all. You see, the whole user-host relationship is easy to understand 
  - IT SHOULDN'T EXIST! It's very simple, don't talk to the host unless absolutely 
  necessary. Don't ask a bunch of questions and don't voice any opinions. They 
  just don't care. If the host talks to you, then of course, talk back, but you 
  shouldn't be an asshole and complain about the unfixable - Speed, messed up 
  Sends, etc. And never under any circumstances, argue with the host, because 
  it won't last long. As soon as you say something like that you will get banned. 
  Hosts don't wanna hear it. The whole act of complaining to a host will be discussed 
  next, but you really shouldn't have much to complain about except something 
  being wrong with the Script (like not getting credit for uploads, nothing sending, 
  etc.). It comes down to this: The host is doing you a service by hosting the 
  fserv so you really don't have that much room to run your mouth to him. And 
  most aren't open to open to constructive criticism or any suggestions so just 
  do your business and leave. It's almost like prostitution: You upload (Pay), 
  then you download (Fuck),then you leave. So do your business and leave. And 
  follow their Rules Message, that's why it's there. <br>
  <br>
  <b><a name="20"></a>C. The Proper Way to Send Complaints</b><br>
  <br>