@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+hagen
+orignal
+postman
+weko
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
FreefallHeavens
Irc2PGuest43975
Irc2PGuest48909
Irc2PGuest67564
Nausicaa
Onn4l7h
SoniEx2
T3s|4_
Teeed
anon2
b3t4f4c3__
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
goose2
goose2_
hk
itsjustme
j6
not_bob_afk
numberwang
onon_1
poriori_
profetikla
qend-irc2p
rapidash
shiver_
u5657
unwr
veiledwizard
w8rabbit
wetpussy
x74a6
zzz
other than (possibly) SAM, I don't believe tunnels is anything we need to coordinate about
orignal
not coordinate
orignal
I'm asking conceptually
orignal
let me ask another way
dr|z3d
orignal: conceptually, retain 4,0 for http client proxy, set 4 for everything else. easy.
orignal
do you have any particular reason to keep 0?
orignal
yes I understand this part
orignal
I don't undertand why to keep 0,4 for servers
dr|z3d
we don't, canon doesn't, the only real issue is SAM, apparently.
orignal
if I understand right Java-I2P stiil has 0,4 for servers
dr|z3d
did you review git.idk.i2p/i2p-hackers/i2p.i2p/-/blob/master/installer/resources/i2ptunnel.config ?
dr|z3d
disregard postman's servers, they're in the process of being updated.
dr|z3d
(in the default configs)
zzz
I don't know off top of my head what the default is for various (new) tunnels
zzz
but use caution because postman changed his tracker to 4 only last year, afaik at drz's recommendation and without announcement, and it caused a ton of downstream client issues for months
dr|z3d
mail servers have been using 4 for a "couple of years"
zzz
but for new tunnels, 4 only seems safe
orignal
ilita is 4 only for few years
dr|z3d
same for irc.
zzz
trackers are unique by having a wide range of diverse clients, more than any other application afaik
dr|z3d
the issue with postman's tracker wasn't the transition from 4,0 to 4, in any event.
dr|z3d
the issue, such as it was, was the removal of the alt DSA dest. different issue.
eyedeekay
I pinged postman earlier today when dr|zed pointed this out, according to him he is on 4 for IRC and Mail already
orignal
DSA is another story
zzz
ok I stand corrected
orignal
my plan is remove 0 from code
orignal
because too much mess with it
zzz
well, that's up to you, I recommend an assessment/survey to see what % of users you might break (and that's my same answer for SAM)
orignal
for SAM definitly 0,4
zzz
which is my generic advice for any removal of old stuff
orignal
yes, that's the first step to use 4 by default
zzz
SAM is a special case, as it's all mostly hidden from the client; but it's easier to keep things as they are now, than it is to try to find a survey all the clients and libs
zzz
if you change anything in your SAM implementation, send me a patch to the spec with info/notes/warnings
orignal
going to use 0,4
orignal
I have 0 by default
orignal
if no objection
zzz
I'm not objecting but I'm not-not-objecting, it's on you to figure out what the consequences are if any, I can't assess that for you
orignal
I don't see why 0,4 could hurt vs. just 0
dr|z3d
0,4 will be fine.
dr|z3d
zero issue offering alternatives, the issue may be in removing 0 altogether if clients are only using 0.
dr|z3d
nothing a rejig of the client can't fix, anyways.
dr|z3d
"my SAM client no longer works" - "make sure it's using 4 as the leasesetEncType, not 0.
dr|z3d
"
orignal
if 0,4 it can't connect to old clients with 0
dr|z3d
0,4 will connect to 0 or 4.
dr|z3d
it should try 4 first and fallback to 0 if 4 unavailable.
dr|z3d
if your implementation isn't doing that, it's doing it wrong.
orignal
if other side supports 4 it will be 4