@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dolphinandcat
+dr|z3d
+goose2_
+hagen
+orignal
+postman
+weko
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
FreefallHeavens
Irc2PGuest48909
Irc2PGuest69244
Irc2PGuest71836
Nausicaa
Onn4l7h
SoniEx2
T3s|4_
Teeed
anon2
b3t4f4c3__
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
goose2
hk
itsjustme
j6
numberwang
onon_1
poriori
profetikla
qend-irc2p
rapidash
shiver_
u5657
unwr
user
veiledwizard
w8rabbit
x74a6
zzz
while I wait for eyedeekay...
zzz
weko, orignal, none of the alternatives in your proposal address the problem of fake RI with old version
zzz
it's useless without that
zzz
I have an idea I'll explain later, but think about it...
eyedeekay
Ack re: Debian changelogs, pushed moments ago
eyedeekay
my news server will be up-to-date in a moment, ech's shortly after
zzz
thanks
zzz
eyedeekay, it's wrong, it has 'bionic' in there
zzz
that would never have worked
zzz
should I just change it, or do you have the real one somewhere?
eyedeekay
I just changed it
zzz
ok, will pull again
zzz
looks like you flipped, torrent is popping off here
zzz
focal sent off to launchpad test PPA
zzz
you have your http su3 in place, right?
orignal
zzz, disagree
orignal
at some point we start honoring floodfills with version > x.x.x
orignal
like we did in past
zzz
right, but that would be a year or more away. we need something that works right away
orignal
nobody say it's a instant fix
orignal
its long term for future
orignal
what's an issue now?
orignal
use my way
orignal
I don't connect through SSU2 to new routers
orignal
until it's confirmed
orignal
one for 3 ways
zzz
and maybe longer for non-floodfills
zzz
and your proposal doesn't say that
orignal
1. Incoming connection
orignal
2. Outgoing NTCP2 connection
orignal
3. Tunnel build reply
orignal
no, it doesn't
orignal
but I'm saying what we do in 2.52.0
zzz
the "confirmed" stuff is messy, and not so easy for us, we need something better
orignal
doesn't matter if a router is floodfill or not
orignal
why is it messy?
orignal
what is not clear?
orignal
connect through NTCP2, if connected that it's good
orignal
got incming connection it's also good
zzz
it's clear, but we don't track those things now, and it's an ugly workaround that's not good for the network
orignal
but I don't know if you check IP
orignal
we track this in profiles
zzz
if we're changing the protocol, we need a complete fix, not rely on a workaround for a year
orignal
that's what I keep saying
orignal
we need to fix SSU2
zzz
right
orignal
then it's easy
orignal
once the fix is in place
orignal
don't create outgoing SSU2 session to older versions
zzz
I know how to really fix it, I'll explain it later this week, working on a release today
zzz
just wanted you to start thinking about it
orignal
about what exactly?
eyedeekay
Yeah my su3 is in place at mgp
zzz
no, I don't want that restriction about older versions, except (maybe) for ff
zzz
I agree with you, fix SSU2, we're all standing by for 2nd draft of your proposal
orignal
then I'm a shrimp ))
zzz
thanks eyedeekay. Do I dare claim on twitter that bundle will be ready "soon", or you still fighting things?
orignal
I don't know how to fix it without restrictions
orignal
I'm busy at work right now
orignal
and don't have time
zzz
well, first you have to fix it to get rid of all the alternatives and tell us what you recommend
zzz
not asking that you do it today ))
zzz
but if you want it for next release we need to get un-stuck soon
orignal
we agreed about extra MixHash and flag I presume
zzz
no, we haven't agreed on anything, and I won't until we have a real review of an updated proposal
zzz
with specifics
zzz
eyedeekay, the build farm queue is 10 hours for ppc, 30+ hours for arm, and 3 days for s390x, hopefully most are lower priority than us, but who knows
zzz
should we add riscv64? are there any chips out there yet or is it still emulators?
zzz
its queue is 4 days though...
zzz
ok, unless/until our launchpad builds finish, I'm done for the day, later...