IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/11/24
@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_
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
zzz more release deliverables + enhancing the newsxml generation scripts, yeah, worse
dr|z3d you love a challenge :)
not_bob At least you are not doing it in perl.
zzz your proposal is to write UI code to put the i2p release process into the console itself? that's the most batshit thing I've ever heard
dr|z3d haha, no. my proposal was a plugin to make your life easier composing the news.xml feed.
dr|z3d but I'll take the praise where I find it :)
zzz that's a subset of 'release process'
dr|z3d I guess the other part of the plugin would handle the torrent generation leveraging existing build.xml targets. but it was just a throwaway suggestion, not a firm proposal. :)
zzz you've heard this before, but if only you had a fork...
dr|z3d I don't worry myself with any of that right now, update.zip works fine here :)
zzz need a script to generate news.xml from mastodon timeline
dr|z3d mastodon. you're hedging your bets with twitter?
not_bob Now that Trump is back, twitter has a future! Not a good one.
zzz haha not until I find some server I trust more than elon's
zzz we'll see
dr|z3d or you're one-upping my batshit? :)
zzz not_bob, did you abandon your quest to be on the console home page?
not_bob zzz: No, just got busy and never submitted a proposal.
not_bob And I could not make it to the last meeting anyway.
zzz ok, your next chance is Feb. 7 meeting
not_bob Sounds good to me.
not_bob Did you see I'm now a jump service on i2pd?
zzz sure, why not
not_bob I will also run the numbers run numbers at the end of the year for stats.
not_bob Last year I handled about 1/3 of all the jump traffic
zzz I'm at about 83K YTD including no-host-in-form which is a significant %
not_bob I don't know my stats right now. I can look them up later. It's a bit involved with the multi-homed nature of my site.
zzz ditto
not_bob But, 100% uptime!
not_bob Or, at least reachablity.
dr|z3d I'm seeing unclosed <span class="multiOption" tags in editClient.jsi zzz.
dr|z3d last one's also missing a closing </span>
dr|z3d you only need one of those per radio group. it's a container span.
dr|z3d actually, my bad, the multiOption class is per radio.
dr|z3d next up, toggle for auto-refresh on the /peers pages.
dr|z3d wrong window, sorry.
zzz re: span, thank you very much
dr|z3d np, zzz. got a couple of observations/suggestions re the peer connections table.
dr|z3d firstly, and this one also applies to the ntcp/ssu tables.. if ipv6 is disabled, those columns should be hidden from view.
dr|z3d secondly, the status of the transports, for ipv4 and (if enabled) ipv6, could be indicated in the peer connections table. "ok/testing/firewalled"
dr|z3d I've got the active period down to 1m for peer connections to keep those transport tables slightly more manageable, and given how big either transport table can get over time, I've removed the "All transports" page entirely. That's a "might be worth thinking about" class of change :)
zzz reasonable. dunno what an all transports page is
dr|z3d all transports is both the ntcp and ssu tables on the same page.
zzz not in canon
dr|z3d oh, very good then. I remember it being there before, but I guess you must have changed it.
zzz don't recall it, but no matter
dr|z3d yeah, fine fine. if it's not there, doesn't need removing.
zzz if you like your info page why you taking my new peer status tab?
dr|z3d I do like my info page, but the peers tab has a different scope.
zzz ok. thought you were trying to sell me on putting all your info stuff on there
dr|z3d I've rebranded it as "Summary" and it's a great landing page for /peers to ensure you're not loading a huge table and waiting minutes for it to load.
dr|z3d no, no. info page handles the the local transport addresses and the upnp info, I think that's a better place for it. 3 tabs for /peers, summary/ntcp/ssu
dr|z3d whether banned peers should be on /profiles or /peers is a tossup right now.
dr|z3d to clarify, /info right now is all about the local router and system, mostly static info.. config options, jvm, discovered addresses.
dr|z3d the other recommendation for your peers status page is to put the transport limits .infohelp at the top of that page. pads it out a bit, makes it front and center on /peers, keeps it away from the other pages.
dr|z3d it should also fix any margin issues you might have with the table alone on that page.
zzz I'll delay the layout fixes until we finalize what's on it