@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+dr|z3d
+eche|off
+hagen
+not_bob_afk
+postman
+snex
+wodencafe
Arch2
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest70083
Irc2PGuest96449
Irc2PGuest97049
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
T3s|4__
acetone_
aeiou
ardu
b3t4f4c3___
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
eyedeekay_bnc
mareki2p_
onon_
orignal_
phobos
pisslord
poriori_
profetikla
qend-irc2p
radakayot_
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
zzz
no thanks, I agree w/ R4SAS on that
zzz
you're crusading against full scrape but for an html replacement that does the same thing? I don't get it
dr|z3d
no, it doesn't do the same thing.
dr|z3d
the html page only presents a subset of hashes, only those that are active (one or more leeches).
dr|z3d
(in addition to more finegrained stats on the tracker connections)
zzz
it's substantively the same
dr|z3d
I disagree. There's a huge difference in presenting all hashes, and only those hashes that are active.
dr|z3d
And there's a substantive difference in presenting hashes as html vs a scrape url.
dr|z3d
I pencilled in the possibility of putting the hash list behind an http auth p/w as an additional protection.
dr|z3d
zzz: around line 190 in ZzzOTController.java, just a couple of lines to comment out.
dr|z3d
//UDPHandler udp = new UDPHandler(_context, _tunnel.getTunnel(), _zzzot);
dr|z3d
//udp.start();