Start your own public tracker

Well that answers my question! What does System do in his spare time? Very VERY cool of you to post this Thanks so much.

This will somehow be corrupted and misinterpreted as a new RVT tracker maybe R3vol7 v2.0 or something and shoot right up to a level 13 like Mango.
 
Lope333 said:
you're right about the capcha thing. simply having a non-standard forum will prevent most automated spam bots.
Click to expand...


A spam bot can be modified to work with any forum, so a non-standard is not the answer.

I created something a year or so back called anti-flood code, and is designed to only allow x torrent comments, forum posts or personal messages to be sent every hour. Once that limit has been reached, no more submissions can be made until cleanup is run (whereby a percentage of the sum is reduced).

A similar system, based on my own, was submitted by ScarS, which again restricts the number of allowed postings (or messages or torrent comments).

My system allows me to change the maximum value for each attribute, so a persistant forum spammer can easily be restricted to one post per hour, whereas a valued contributor can have that value increased to whatever we felt would be benefitial.

Along with that code is another bit of code that restricts how many times a client can announce, which is also another form of flooding (when it is done repeatedly).

All this, and more, can be found on TBDev.net...
 
You could change the function error in announce.php to something like:

function error($msg){
if($msg==='Database error') $msg.=': '.mysql_error().' '.__LINE__;
header('Content-Type: text/plain; charset=ISO-8859');
header('Pragma: no-cache');
die('d14:failure reason'.strlen($msg).':'.$msg.'e');
}

This would output the message "Database error: " followed by the error as reported by mysql and the line number.

Because the error message may be longer than uT wants to display, you should log it with a packet sniffer. http://www.analogx.com/contents/download/network/pmon.htm is a nice simple one.
 
could someone please signup and check if my
torrents work? i think there is somthing wrong
there, maybe the problem is when i upload, do
i have to use my website adress/announce.php?
 
Hello friends i need your help please
i just wanna have make only very small my home torrents for my friends like mininova.org is just check: http://hometorrents.100webspace.net/
i need only seed/leecher script please help me i dont care if there someone will not upload his/her files just i will upload only i wanna fix only only seeder/leecher script can anyone teach me this code or script?thanks before
 
For the encore, here's how to switch the banlist into a friendlist by adding a single character:

Open announce.php
find: if(isset($bans[$ann['ip']])) error('You are banned');
change it to: if(!isset($bans[$ann['ip']])) error('You are banned');


Now, only the IPs you add to the ban list are allowed to use the tracker.
Others will still be able to see and download torrents, but only your friends will be able to actually run the torrents :)
 
Gonna start working on a new version, so anything you want adding just let me know.

I'm likely going to drop the mysql requirements completely, throw in a setting to either be black or white listing (bans or allows), add a setting to allow tracking of torrents that aren't uploaded simply by announcing to the tracker, and maybe build a multi tracker address adding service (upload the torrent, get it back with a list of multiple trackers embedded).
 
misledhope said:
nice work rvt :) the community owes you alot. next time your bored you could get in touch and help out w/ gazelle perhaps ;)
Click to expand...

seeing as though gazelle is going to be open source and is hoped to be a serious replacement to tbsource i'd hope that what.cd would be seeking input from other site coders. glad to see such a public invitation to help develop gazelle further, not that i doubt whats coding skills.
 
Been working on it flat out. Lots of fairly big code pieces are getting done at the moment. Mostly backend stuff, like a proper ip to name function that doesn't block a page for minutes at a time, integrating maxminds geoip ip to country, fully working utf-8 support, url/ip/email validation are all done.
Also done a whois lookup page for mods, so they can click an IP and see the ISP name etc, even when PTR lookups fail.

Security is mostly done. Auto logouts when your cookies are used from a different address, blocking of brute force attempts on login/cookie login/password recovery/email change validation etc. Currently adding in a session based verification for mod functions to prevent mods being tricked into doing something from an external link.

I'm putting in some intelligent caching, whereby the cache is actually a php file. An example of where it's useful, a profile page. Normally, you want certain parts of a profile only accessable to staff, like mod comments. If you cache the HTML output, it's either missing the staff parts, or they become accessable to everyone. Storing as a php file allows us to keep the seperation while storing all the data preloaded and preparsed.
Works nicely on the news page as well, where you have a lot of bbcode() calls that can be cut down by caching but also want links to edit/delete only for admins.

It has 2 stage access control. There are mod/torrent mod/admin and sysop flags for classes, as well as class numbers. You can have a sysop at class number 1000 say, and an admin at 2000. The admin still only gets admin access, but can alter the sysops account. It allows you to make a coder class with sysop privs (can see everything), but have the coders account settings accessable to the admins.

I've built a setup script for it, which should run you through everything easily. All that needs doing on that is plugging in the sql queries once the code is finished.

Been building this one on windows with php4, and testing with linux and php5. Testing on apache and lighttpd. It should be more reliable, although it might be better running it on a VPS or paid for webspace rather than free space.

This version will be definately aimed towards private sites. Once this is finished with, I can start replacing the private stuff with public stuff.


setup1.jpg


setup2.jpg


setup3.jpg


setup4.jpg


profile.jpg


profile2.jpg
 
Back
Top