dr|z3d
that's an accurate calculation, orignal :)
dr|z3d
minimum 3 month development cycle for major releases unless something catastrophic requires an early release.
orignal
or skip a release))
dr|z3d
sure, I don't think that's ruled out if that keeps java in sync with i2pd, api version wise.
orignal
we usually try to keep the same version
dr|z3d
shiver: was it you before reporting high cpu usage for the sidebar refresh?
dr|z3d
what up y2kboy23
y2kboy23
dr|z3d hey
dr|z3d
all good over there?
y2kboy23
Yep :) and you?
dr|z3d
not bad thanks, not bad. any more issue surfacing now you've found your browser's console panel? :)
y2kboy23
I have not seen anything strange.
y2kboy23
I saw the sidebar issue but I think you fixed that
dr|z3d
which issue was that?
dr|z3d
still a few gremlins lurking..
dr|z3d
and maybe just as importantly, does it all feel faster, the sidebar and generally browsing around the console?
y2kboy23
On my phone, I can certainly see a speed increase.
y2kboy23
The LA/ram sidebar graphs look off to me.
dr|z3d
off? in what sense?
dr|z3d
graphs, or bars?
y2kboy23
The bars
y2kboy23
Might just be me and short uptime on my router. I'm usually see something on them. They look stoic right now.
y2kboy23
They're working just fine.
dr|z3d
couple of things I'm still trying to figure out. progress bar for in console updates, not sure if that's working right now, and the toggle links/magnets function in snark is hit and miss.
y2kboy23
That line at the top that runs from left to right? I've seen that before.
dr|z3d
still, if the console feels faster on your phone, it's not all bad.
dr|z3d
no, that's the page loader, that's fine.
dr|z3d
you probably don't see the update bar if you're building docker images, it's only displayed when you update in-console.
y2kboy23
Ohh, yea. Docker is different with updating.
dr|z3d
ok, well, touch wood all the other issues should be fixed.
dr|z3d
javascript-wise, that is. still some upstream fixes I'm waiting for to resolve various other issues, but that's out of my hands.
y2kboy23
I'll keep an eye out for things but I haven't seen anything else at this point.
y2kboy23
I miss the flags..
dr|z3d
you and me both :)
dr|z3d
but in the absence of flags, there's no reverse dns with a local cache which should make it a lot less laggy.
dr|z3d
*now
dr|z3d
flags hopefully back soon, that's the upstream part I mentioned earlier.
y2kboy23
I never ran the reverse dns so I'm unfamiliar with that lag
dr|z3d
well, before it was performing a lookup to the local DNS resolver every time a widget required it.
dr|z3d
now it does that once, and then caches the result to disk, so subsequent lookups should be instant and page loading lag minimal.
dr|z3d
if you do enable it, there's a readout on /info that tells you the state of the cache.
dr|z3d
(cache is in ram, disk cache ensures persistence inter-session)
dr|z3d
full cache, 32K entries, approx 1MB.
y2kboy23
ohh, nice. maybe i'll give it a shot.
dr|z3d
routerconsole.enableReverseLookups=true
y2kboy23
And...I just went through every config page looking for an option to enable...
dr|z3d
advanced feature, that one, though I may add a toggle at some point in the UI.
NarratorZ
a long time...
RN
far far away...