Open Torrent Tracker Project Files

===============================================================
OPEN TORRENT TRACKER PROJECT. v0.03 by 0e8h
===============================================================
===============================================================

===============================================================
SOME LEGALS.

(#Reader or Potential-User) I understand ...
1) This package, program, system, means of process, is called 'Open Torrent Tracker Project' or, 'OTT' or 'OTTP' for short, and has ownership and owner-rights of the original maker.
2) Copyright is reserved, and stipulations entail, to 'Open Torrent Tracker Project', devised by its Owner!
3) You must keep up to date on the stipulations of OTTP use.
4) Use, when given, only covers beneficial outcomes. It is the duty of the person executing 'OTTP' to fathom its implications and take its burden and any damage caused.

(#From the Owner.) Having said the above I allow anyone to use OTTP, as long as when changes are made, the code changes are submitted as a recommendation of change to the original package/project. You also need to promote OTTP.

I am unfamiliar with Creative-Commons agreements and may later place OTTP into one of their protective orders.

===============================================================
BASICS.

'Open Torrent Tracker Project' is a simple bittorrent tracker. It maintains hash data supplied by inquiring bittorrent clients.  OTTP accounts for the number of enquiries and returns that data to the clients, when asked.  No torrent specifics are needed, or taken, only hash data, socket data, and some modes, are suffice.

OTTP allows you to run your own open bittorrent tracker without the need of a html website, where conventionally people would upload torrent profiles that would have reflection to the hash database.

OTTP allows you to take no part in censorship or vilification of torrent content.


===============================================================
SETUP.

1) Copy main directory of files to your server directory, planned. No need to copy '/setup' (Hint, your domain name points to this!)

2) Use mysql.sql file in '/setup' to import tables into a newly created MySQL-Server database.

3) You may need to create a MySQL user account if running a dedicated server or you want to isolate the script access from other projects.

4) Edit db_sets.php to suit your database name, username, and password, etc.

5) Configure your server's 'php.ini' to suit. Example turn off magic quoting, and increase timers to support longer processes. Dedicated server owners could reduce timings in config.php.

6) Configure your server's Apache setting or '.htaccess' files to suit. Example '.htaccess' can be used to rewrite 'announce' to 'announce.php' in URL calls. Note the 'htaccess' file in '/setup' needs to be renamed with a '.' at the start, example '.htaccess'!

7) Promote your tracker by releasing the URL, (this means the location of the announce script,) to the wider internet.

8) Further promote your tracker by adding a html webpage for your tracker's domain.

9) Promote OTTP, by putting our logo on your webpage!

10) Ask for donations if you wish.

11) Watch the peers and hashes come in... enjoy your assistance to the bittorrent community!  Learn the meaning of life!


===============================================================
NOT WORKING!

FAULT) 'PHP server incompatibility. Turn off magic quotes!'
POSSIBLE ANSWER) Adjust your php.ini so that magic quoting in off. There is a php.ini example in '/setup'. Note the example is only for needed commands, so don't over write your existing 'php.ini' !!!


===============================================================
WHAT OTTP DOES NOT DO!

* OTTP does not ip filter. So use ISP hacking protection or setup your own firewall to protect the scripts and databases.

* OTTP does not protect against ip-miners, other than setting a minimum time of access to a particular hash record by same ip.  IP filter to somewhat stop non sharing participants.

* OTTP was not written to support IPv6, but may work.  I would need to look at the protocol again and see how it would fail or succeed. I have left space in sql database to cater for IPv6.

* OTTP does not server farm, but you could separate the database into various subs, then change code to suit the discernment needed.

* OTTP could serve many thousands of accesses, but timings must suit server and memory, ability.

* OTTP is not written with Microsoft in mind.


===============================================================
DEVELOPMENT DETAILS!

http://ottp.sourceforge.net

svn co https://ottp.svn.sourceforge.net/svnroot/ottp ottp

===============================================================
CHANGE LOG

v0.01 Release
v0.02
* Adjusted new peer announce cycle timing
* Added script version
v0.03
* Fixed announce by renaming 'peer_id' to 'id_peer' in announce.php
* Reworked mysql.sql so that it has basic table includes
* Added basic php.ini and htaccess files for examination
* Modified bigint(1) to int(1) for table id's and their referencing. BigInt is way too big.
* Added php magic quote checking and error string
* Adjusted hash variable checking