so i'm going to run azureus on my server with a web interface. i'll offer user accounts to you guys. we'll share the cumulative downloads, and this provides you with a great way to seed up your ratio.
ideas on rules?
ideas on rules?
ttf posters get accounts :D
i want to
well, i'm going to integrate the interface into ttf
excelent
my idea on rules
1. ttf users do not get torrent access on registration.
2. each ttf user gets a base quota (maybe 500MB), which can be increased with a small donation (i'm not rich--VPSes cost money)
3. a ttf-torrent user may log onto supported trackers (like oink, demonoid), search for torrents, and download them
4. they can then upload them to the ttf interface, which replaces the user's passkey with ttf's passkey
5. ttf will leech insofar as the ttf-torrent user's disk space permits, and it will seed.
6. once leeching is complete, it will appear as a download from the ttf server to all users via http.
7. if three people total download the resultant file, it will be flagged as a community file. the file will be removed from the user's disk space, but kept on the server for continued seeding (which helps prop up ttf's ratio with the tracker) and for continued downloading by ttf users.
8. if less than three people download it, the ttf-torrent user who queued the torrent may delete it once it has reached a 1.0 ratio.
[p.s. sorry about the downtime lately. i'm upgrading the os from ubuntu 6.06 to the new ubuntu 7.10]
1. ttf users do not get torrent access on registration.
2. each ttf user gets a base quota (maybe 500MB), which can be increased with a small donation (i'm not rich--VPSes cost money)
3. a ttf-torrent user may log onto supported trackers (like oink, demonoid), search for torrents, and download them
4. they can then upload them to the ttf interface, which replaces the user's passkey with ttf's passkey
5. ttf will leech insofar as the ttf-torrent user's disk space permits, and it will seed.
6. once leeching is complete, it will appear as a download from the ttf server to all users via http.
7. if three people total download the resultant file, it will be flagged as a community file. the file will be removed from the user's disk space, but kept on the server for continued seeding (which helps prop up ttf's ratio with the tracker) and for continued downloading by ttf users.
8. if less than three people download it, the ttf-torrent user who queued the torrent may delete it once it has reached a 1.0 ratio.
[p.s. sorry about the downtime lately. i'm upgrading the os from ubuntu 6.06 to the new ubuntu 7.10]
so would there be a ttf account or something on oink? that doesn't help my ratio out at all :).
it does, actually. say i use the ttf-torrent service to leech torrent X via ttf. then you login to ttf and download the files from the ttf server. then you download the matching torrent file from oink, and you seed it without touching your leech count on your oink account.
huh, that's interesting. I wonder if oink would care.
my original idea when reading the thread was a web interface to Azureus that I could use personally. which would be neat because then I could leave stuff seeding all the time. I'll probably do this myself eventually, minus the web interface, on my server.
my original idea when reading the thread was a web interface to Azureus that I could use personally. which would be neat because then I could leave stuff seeding all the time. I'll probably do this myself eventually, minus the web interface, on my server.
that would be cool, but i dont think one IP can use multiple passkeys.
good point! you can't use the same passkey with multiple IP addresses either. that = ban.
not true.
http://oink.cd/faq.php#userm
Multiple IPs (Can I login from different computers?)
Yes, the tracker is always capable of following sessions from different IPs for the same user. A torrent is associated with a passkey (which is included inside the .torrent file). We always know who you are and your stats will not be mixed up with anyone else with a similar IP address.
http://oink.cd/faq.php#userm
sorry, I meant to specify simultaneously. pretty sure that is grounds for a ban.
really? :/
Sounds smashing to me.
[A]s soon as 4 different people with your passkey (on different IP addresses) try to use the same torrent at the same time, your account is automatically disabled. The addresses will be logged in your account so a staff member can see them. If in fact it looks like you shared a torrent file, you won't be getting your account back again.
from http://oink.cd/trackerinfo.php under "Is there anything I need to be careful of?"
so we're cool, yeah?
I rather share with people I trust than random people on the web. I'm more loyal to you guys so I won't cut you off.
yeah, this idea would be cool. my idea probably wouldn't get one banned but it's kind of against the rules.