@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BravoOreo
BubbRubb
Chrono
Danny
FreefallHeavens_
HAON
HowardPlayzOfAdmin
Irc2PGuest12250
Irc2PGuest28321
Irc2PGuest28800
Irc2PGuest29346
Irc2PGuest32123
Irc2PGuest39834
Irc2PGuest82196
Leopold_xmpp_
Onn4l7h
Over
ScavengerGetting
SigSegv
Sisyphus_
Sleepy
T3s|4_
Teeed
acetone_
ardu
b3t4f4c3__
bak83
dr4wd3
duanin2
duck
eyedeekay_bnc
kaffi
makoto
mareki2p_
nilbog-
nnm--
ohThuku1_
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
u5657_1
uop23ip
w8rabbit
wew
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();