Automate requests for binaries to be posted on newsgroups which fall under the structure of The Binary Network. Allow users to communicate away from the news servers. To minimize and hopefully eliminate redundant posts.

Here are some of the things you need to know to make sense of the channels. First off, this FAQ is specific to this Network and in no way should be taken as a walkthrough for first time Internet Relay Chat users. For a proper introductory tutorial, try this and remember, you and only you are responsible for your own privacy.

Usenet is a global network of servers that mirror each others content. The content on Usenet is divided into "newsgroups" (eg. alt.binaries.multimedia), and each newgroup contains "articles" or "posts". The posts can be either text or binary. You are here because you are interested in binary.

You need a newsgroup server, and client.

You will need to subscribe to a server, commonly referred to as an NSP (News Service Provider). This costs money - usually $15 - $25 USD a month depending on the NSP you choose. Costs mostly differ due to two factors, download allowance and retention. Download allowance is how much text and binary data you are allowed to download during that month. Retention is the number of days that your NSP will keep the binary data around before deleting it. The more download allowance and higher retention, the more costly the NSP per month. Type ?? nntpserver in the channel to get our current recommendations.

NNTP is to Usenet what HTTP is to the World Wide Web. To download posts from Usenet you will need an NNTP client. Type ?? nntpclient in the channel to get our current recommendations.

Millions of articles are posted on Usenet every day. So you don't have to download all of the summaries to find out what is available, a special file called an NZB can be used to download a single set of articles. (ie. a TV show) When opening the NZB file through your NNTP client it will automatically know which articles to download. NZB files are created by hand and are available from various sites around the web, some free, some not. Type ?? nzb in the channel to get our current recommendations.

You need to start configuring your settings.

Open your NNTP client. Find the Options or Configuration screen. Put your login details for your NSP in the right place. Adjust any other options like your local download directory, etc. Don't change options that you don't understand.

Get an NZB of a TV show you want to download. Make sure that it is not older than your NSP's retention.

Import the NZB file into your NNTP client. It should begin downloading your test TV show.

Well, you should know what you're downloading, but make sure its completed, if not using par(2) files to recover/repair.

RAR files are multi-part archives. Imagine a ZIP file split into many parts - essentially the same thing. To "unpack" or "decompress" the RAR files you will need to install a RAR-compatible program. Type ?? rar in the channel to get our current recommendations. Open the main RAR file using your program. It will be called either example.tv.show.s0Xe0X.rar or example.tv.show.s0Xe0X.part01.rar Extract the AVI file contained in the archive to your hard disk. Your TV show is now ready to watch.

Due to the nature of Usenet, every so often your RAR files may be incomplete or damaged. Contained within your NZB should also be a set of PAR(2) files. These files are used to repair your RARs. To use the PAR(2) files you will need to install a PAR(2)-compatible program. Type ?? par in the channel to get our current recommendations. Open the main PAR(2) file using your program. Repair of your RAR files should begin. Once completed succesfully, you may attempt to unpack the RAR archive again.

Make sure you request the correct release in the proper channel.

First off, each channel is different but similar for requesting. You need to know the title and the filecount of the movie/show, which can be found on NFOrce. It makes life easier for everyone if you do your homework first, and make sure you request a scene release, we do NOT accept homemade crap.

The use of this, makes life easier. It is a matter of cleanliness. Making a request to any newsgroup should be made in the proper channel which are done through the request bot (Bin-Req) by typing: -addreq (Full or Part) (Filecount) (Your Request).
Ex: -addreq Full 94 Welcome.Home.Roscoe.Jenkins.DVDR-Replica
Ex: -addreq Full 13 Family.Guy.S05E01.PDTV.XviD-TV

For starters, someone else must have what you are looking for and be willing to post it to newsgroup. Which means, the posts can take quite a while to propagate themselves across the Internet. It is a safe bet to wait anywhere from 12 to 24 hours after the fill has been marked as completed by the Bot for all of them to appear on your server.

Make sure you request the correct release in the proper channel.

You must include a PAR/PAR2 set with every full post. A ratio of 10% PAR/PAR2 files is required and will help ensure that everyone is able to complete and/or rebuild any missing files. FSRaid creates .par files. Quickpar creates .par2 files. You must also include the NFO/SFV/NZB with your post.

Unless the index page of a specific group says different this is what you should have:
#Channel on EFNet Presents: REQ XXXX - Whatever It Is - $1/$2 - $F
EX: #Alt.Binaries.MultiMedia on EFNet Presents: REQ 50000 - Family.Guy.S05E01.PDTV.XviD-TV - $1/$2 - $F

Tell the Bot you are filling the request, by doing "-filling XXXX". Then post the request to the appropriate newsgroup using the guidelines above and then tell the Bot when you are finished filling, by doing "-filled XXXX". Abusing the bot or cheating will result in a perm ban; this is your first and only warning, we will not tolerate cheaters nor childish activities.

Yes, as long as the Bot knows that it was you, which you will be credited points per fills and a better User Level.

On your bottom left side, click on Commands which lists every command the Bot understands, along with examples of how the syntax works. Simply type the command including the - at the start and any required syntax for the command into a single line in the channel and the Bot will respond accordingly.

Simple, by filling requests. What are you, new? Also, tell your friends about the channel. The more aware people become of this channel, the stronger it will become as it is powered by people. The files don't post themselves. If you wish to donate cash, the ops also accept US money orders and gold bricks at their post office box located in Vladivostok, Russia. Ask a channel Op for more info.

Requesting and filling limits are for a reason.

To prevent people from leeching all the time and not giving back. To be able to request more, then please help and support the channel and give back by becoming a filler and to get a higher user level.

User Level	# of Request Allowed	Points Required	Description
Leecher	3	0	It applies for the new users.
Filler	5	1-499	It applies for the low fillers.
Filler	10	500-4999	It applies for the mid active fillers.
Filler	15	5000-9999	It applies for the active fillers.
Filler	25	10,000+	It applies for the highly active fillers.

Yes, a limit was set to make it fair to other fillers. Other fillers need a chance to be able to fill some requests by adding the limit; to stop fillers from hogging Requests that their not going to fill for days. It doesn't mean you can't fill, just need to be able to keep your uploads to a minimum. It also makes sure that the request get filled within the 4 day time limit and prevents user from going elesewhere.

User Level	# of Fills Allowed	Points Required	Description
Leecher	2	0	It applies for the new fillers.
Filler	3	1-499	It applies for the low fillers.
Filler	5	500-4,999	It applies for the mid active fillers.
Filler	7	5,000-9,999	It applies for the active fillers.
Filler	10	10,000+	It applies for the highly active fillers.
Filler	15	100,000+	It applies for the top fillers.
Half-Op	5	1-499	It applies for the low fillers.
Half-Op	7	500-4,999	It applies for the mid active fillers.
Half-Op	10	5,000-9,999	It applies for the active fillers.
Half-Op	12	10,000+	It applies for the highly active fillers.
Half-Op	17	100,000+	It applies for the top fillers.

Basic step by step on how to request a tv show.

You may request a certain show be posted to Usenet via the bot, if you stick to the following rules:

• The show has actually been released. Search the NFO sites and keep a copy of the full release name handy.
  Type ?? nfo in the channel to get a list of NFO sites.

• The show has not already been posted to Usenet in the last thirty (30) days.

• The show has not already been requested. Double-ups make it confusing for the people posting shows.
  Type -search example.show to find out if your show has been requested already.

Requests are made by typing "-addreq Type Filecount release.name.and.details" in the channel, where Type can be either Full or Part. Full is the whole release. Part is part of the release. (more information must then be given in release.name.and.details). Filecount is the number of RAR files in the release. Type ?? filecount in the channel to get a list of valid filecounts. The release.name.and.details is where you put the release name you found on the NFO site. Type ?? nfo in the channel to get a list of NFO sites.

Once you have made your request, it has thirty (30) days to be filled before the bot automatically removes it. Most requests (especially new releases) will likely be filled very quickly. DO NOT, UNDER ANY CIRCUMSTANCES, ASK FOR YOUR RELEASE TO BE FILLED IN THE CHANNEL. Just in case you don't understand, here it is again: DO NOT, UNDER ANY CIRCUMSTANCES, ASK FOR YOUR RELEASE TO BE FILLED IN THE CHANNEL. Please be patient and your request may be filled, if a poster decides to. The bot will send you a message if your request has been marked as Filling and has finished being Filled.

The common TV sources are DSR, PDTV, HDTV, HR PDTV, HR HDTV, and 720p HR HDTV.

Source: Standard 4:3 (fullscreen) PDTV
Video: 512 pixels wide by 384 pixels high
Audio: 2 Channel MP3
Size (30mins): 175 MB
Size (60mins): 350 MB

Source: 16:9 (widescreen) 1080i HDTV
Video: 624 pixels wide by 352 pixels high
Audio: 2 Channel MP3
Size (30mins): 175 MB
Size (60mins): 350 MB

Source: 16:9 (widescreen) 1080i HDTV
Video: 960 pixels wide by 528 pixels high
Audio: 2 Channel AC3 or 5.1 Channel AC3
Size (30mins): 350 MB
Size (60mins): 700 MB

Source: 16:9 (widescreen) 720p HDTV
Video: 1280 pixels wide by 720 pixels high
Audio: 2 Channel AC3 or 5.1 Channel AC3
Size (30mins): 800 MB
Size (60mins): 1600 MB