@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+hk
+not_bob
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest15271
Irc2PGuest28511
Irc2PGuest64530
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83
boonst
cancername
cumlord
dr4wd3
eyedeekay_bnc
hagen_
khb_
plap
poriori
profetikla
r3med1tz-
rapidash
shiver_1
solidx66
u5657
uop23ip
w8rabbit
weko_
x74a6
mesh
I guess I should upgrade to 2.0
dr|z3d
zzz: checkbox leading followed by config label is the convention in the console.
dr|z3d
label? is bad, hmmkay.
dr|z3d
[ ] Enable gzip log compression
zzz
not on that form, its a table: label input. But consistency isn't our strong suit
dr|z3d
Doesn't matter if it's a table, the label shouldn't be confused with the row title there. It would read roughly Compression | [ ] Compress logs | Help Text goes in third td if desired.
dr|z3d
and you want to wrap the checkbox and label with a <label> tag so you can click on the text label to activate the option.
zzz
disagree, but thx for the comments, early days
zzz
our checkboxes seem to be half round and half square, at random, speaking of consistency
zzz
and not much of an outline
zzz
always more todo
dr|z3d
up to you, anyways, but that's the informal style guide from the person who made the UI consistent :)
dr|z3d
that's on you, not me, the styling long departed from what I implemented :)
zzz
no shade intended
dr|z3d
someone feel in love with border-radius and didn't know how to take their foot off the throttle :)
dr|z3d
*fell
zzz
that's bold of you to call out somebody else's lack of restraint :)
dr|z3d
anyways, you been busy on the commit front, quite a chunk of commits there.
zzz
linux-style merge window
dr|z3d
ah, you're top loading it and riding out the next 2.5 months on the couch? :)
zzz
I see about 3 or 4 config tabs that have the table style
zzz
the compress opt is behind routerconsole.advanced anyway, not too worried about it
zzz
old school working on the next one before this one is done. that's the way it should be
zzz
but isn't always
dr|z3d
sure, always good to have one eye on version.next. speaking of, anything experimental you haven't unleashed yet?
zzz
ofc
zzz
not everything is done on day 1
zzz
mainly the peer selection rewrite promised for 2.0.0 and failed to deliver
not_bob
:(
dr|z3d
re pack200, if it was only the chicken/egg conundrum holding you back from putting in cannon, I figured out a surefire workaround for that. pre-pack200 builds request i2pupdate.{zip/su3} and pack20-capable builds request i2pupdate200.{zip.su3}
dr|z3d
s/cannon/canon
dr|z3d
what's up not_bob?
zzz
that doesn't fix the egg problem with building official updates
not_bob
Not much currrently. Busy day later.
dr|z3d
if you mean official updates as advertised by the in-console news, that would just require 2 separate urls depending on pack200 support or not. only routers with pack200 support would attempt to download the pack'd update.
zzz
that sounds like making my least-favorite part of the job even worse
dr|z3d
compiling the updates and the console news? probably an in-console plugin to handle all that would make that job a bit less onerous.