@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+dr|z3d
+eche|off
+hk
+orignal
+postman
+snex
+weko
+wodencafe
Arch
BravoOreo
BubbRubb
Chrono
Daddy
Danny
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest34005
Irc2PGuest74165
Irc2PGuest7785
Irc2PGuest79267
Leopold_xmpp
Onn4l7h
Over
SigSegv
Sisyphus
Sleepy
Teeed
aargh
acetone_
aisle
ardu
b3t4f4c3__
carried6590
cumlord
death
dr4wd3
duanin2
eyedeekay_bnc
hagen_
mfs
nilbog
not_bob_afk
ohThuku1_
poriori
pory
profetikla
qend-irc2p
r00tobo_BNC
rapidash
shiver_1
solidx66_
thetia
u5657
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();