@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+dr|z3d
+hk
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest21357
Irc2PGuest21881
Irc2PGuest58867
Leopold_
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4_
T3s|4__
aargh2
anon2
b3t4f4c3
bak83
boonst
cancername
cumlord
dr4wd3
eyedeekay_bnc
hagen_
khb
not_bob_afk
plap
poriori
profetikla
r3med1tz-
rapidash
shiver_
solidx66
tr
u5657
uop23ip
w8rabbit
x74a6
zlatinb
hey y2kboy23_ thanks for the docker MR. It's ready to be merged I think, just eyedeekay needs to take a look if there isn't anything extra required from first-time contributors
zlatinb
hmm you probably can't reply cause the channel is +m
dr|z3d
zzz: read toggling panel via entire #configtitle, more hassle than it's worth.
dr|z3d
I think the mechanism is fine enough as is.
dr|z3d
If I was going to change it, I'd put a config icon in the main title on the right instead, to completely hide the configuration title except when toggled on.
dr|z3d
for now, though, not hugely important. add some more features, then maybe it'll make more sense investing the time.
zzz
ok
dr|z3d
any chance we can have an option in zzzot to store the data on disk instead of all in ram?
dr|z3d
would also be good to get a breakdown of number of seeds/leeches, and a count of unique clients vs all client connections.
dr|z3d
option to toggle serving scrape data would also be good, and an option to only serve scrape data per torrent rather than divulging all torrents being monitored.
zzz
disk would be a completely different design, so no
dr|z3d
can you write out the data periodically and reload at startup?
dr|z3d
not quite the same thing, so maybe easier?
zzz
still a lot of work
dr|z3d
do we know how much ram dg's opentracker is using, given it's serving 20K+ torrents?
zzz
no
dr|z3d
ok
zzz
total seed/leech stats isn't very interesting
dr|z3d
I agree, but it's more interesting than just reporting peer connections.
zzz
a scrape option is a good suggestion
dr|z3d
it can be done with the jetty config, but that's not idea.
dr|z3d
*ideal
dr|z3d
and serving up a scrape response currently on dg's opentracker probably isn't great for the server, given you get everything.
dr|z3d
if you were feeling creative, you could throw up a config page and hide it behind httpauth :)
dr|z3d
also, probably worth adding info about tunnel.0.spoofedHost=hostname.i2p to the help file and adding a commented out config in i2ptunnel.config
dr|z3d
once you're done with the changes, I don't mind handling that and updating the help etc. css also needs a refresh.