@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+lbt
+orignal
+postman
+segfault
+weko
+wodencafe
Arch
DeltaOreo
FreefallHeavens_
Irc2PGuest17123
Irc2PGuest30976
Irc2PGuest52978
Irc2PGuest59134
Irc2PGuest99152
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SoniEx2
T3s|4_
acetone_
aeiou
anon2
b3t4f4c3
bak83_
boonst
cumlord
dickless
eyedeekay_bnc
mareki2p_
not_bob_afk
poriori_
profetikla
qend-irc2p
r3med1tz
radakayot_
rapidash
schwarzchild-radius
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
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();