&zzz
+R4SAS
+RN_
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
bob___
cims
dr4wd3_
dr|z3d
duanin2
f00b4r
hababam_
hagen_
leopold
makoto
marek
marek22k
n2
noidea
not_bob_afk
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
zelgomer
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();