User:AzaToth/PRE

A Pre-channel is an IRC channel in which a bot (Pre-Bot) announces new topsite warez (Pre-Announce) releases in real time. Pre-Channels are generally provided as a convenience to members of the scene, often in conjunction with a Topsite or Pre-Scene Network. Pre-channels are typically private, but are continuously infiltrated by Peer-2-Peer Networks in which they are provided for the general public.

How It Works

• There exists beyond the knowledge of mere mortals several dozen networks dedicated to the trading of releases.
• A single person could have a bot on several networks and trading in between each to get the release sent out at an accurate time.
• AddOld: !addold <Release> <Section> <UnixTime> <Genre> <Number Of Files> <Size> <Nuke Reason(If Available)> | Command Send Out After !getold
• GetOld: !getold <Release> | If Your Pre Database Is Missing A Release This Can Be Used to Recover It From Another Bot
• Play: !play --between <ReleaseFrom> <ReleaseTo> | Will Spam !addold Of All Releases From The First Release To The Last
• AddPre: !addpre <Release> <Section> | To Add Releases
• DelPre: !delpre <Release> <Reason> | To Remove Releases
• UnDelPre: !undelpre <Release <Reason> | To ReAdd A Release That Was DelPred
• Info: !info <Release> <Number Of Files> <Size> | To Give Further Info On A Release
• Genre: !gn <Release> <Genre> | To Give Further Info On A Release
• Nuke: !nuke <Release> <Reason> | To Send Out A Mass Message That The Release Does Not Meet Standards
• UnNuke: !unnuke <Release> <Reason> | Often abused, To Send Out A Mass Message That The Release Does Meet Standards.
• ModNuke: !modnuke <Release> <Reason> | To fix a nuke reason without having to unnuke the release first.
• NewDir: !newdir <Release> <NewDir> | Used To Further Complex The Directories and Sections to Allow For A Better Search in The Future.
• SitePre: !sitepre <Release> <Section> <Number Of Files> <Size> | Releases Sent Straight From FTP Sites.
• UpdateTime: !updatetime <Release> <UnixTime> | Used in case the specified release was prespammed, but followed by an actual release at a much later date. This will update the release timestamp to the actual pre date.

Average Pre Channel Commands

• !pre <Release> | Search A Single Release
• !firstpre | First Release in The Database
• !lastpre | Last Release in The Database
• !group <Group> | Return Information On the Group
• !sections | Returns A List Of Sections The Database Includes
• !count <Section> | Returns Information On How Many Releases A Certain Section Holds.
• !dupe <Release> | Search Several Similar Releases
• !db | Shows How Many Releases, Nukes, UnNukes, etc Exist in the Database.
• !hist <Release> | Return all Nuke/UnNuke history for the specified release.
• !ar <HxW> | Return info about the specified Aspect Ratio.
• !howmany <keyword> | Return how many releases are within the database that match the given keyword(s).

Advantages

• Members of a Pre-Channel are notified about new warez/scene releases as they are released. This is of particular benefit to Couriers (Racers) and Release Groups as well as Torrent Sites interested in uploading Scene Releases for their members as fast as possible.
• Pre-Channels commonly announce when a release is Nuked or UnNuked. (Releases are "Nuked" when a release does not meet Scene Standards)
• Pre-Channels provide a search facility that allows users to find out if a release exists, when it was released, and if it has been nuked. This function may also be used by release groups to avoid dupes (duplicates).
• Pre-Channels are also used for Topsites to measure how fast they received the release, otherwise known as the pretime.

Disadvantages

• If a Pre-Bot does not include an elaborate filter to disallow certain words and characters, it can be annoying when defaced with spam.

Access to Pre-Channels

• Over the past several years the difficulty in terms of getting into a Pre-Channel have drastically dropped. Many users apart of certain networks will discover that a public one is available.