~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@not_bob_afk
@orignal
@postman
+FreefallHeavens
+Leopold
+Xeha
+acetone
+cancername
+cumlord
+mareki2p
+poriori
+profetikla
+r00tobo_BNC
+radakayot
+uop23ip
An0nm0n
Arch
Dann
DeltaOreo
FreeRider
Irc2PGuest22448
Irc2PGuest4830
Irc2PGuest73910
KiloDeltaRomeo
Liorar_
Meow
Nausicaa
Onn4l7h
Onn4|7h
T3s|4_
anon2
anu
boonst
enoxa
juicedup
mareki2pb
opaque
qend-irc2p
shiver_
simprelay
solidx66
stormytest
u5657
weko_
woodwose
zzz2
dr|z3d
hi radakayot, welcome to #saltr
orignal
guy who is going to implement own i2p router? ))
radakayot
hello dr|z3d.
radakayot
haha, yes orignal.
dr|z3d
*** pokes orignal ***
orignal
how is it going?
orignal
where you able to establish an NTCP2 session?
radakayot
it's going really good thanks to your implementation.
radakayot
actually I did. now implementing dns server to resolve i2p domains to pseudo ipv6 addresses.
orignal
so no new implemntation of i2p router
radakayot
i had to borrow total of 13 files from your implementation of course.
orignal
only 13? I doubt that's all
radakayot
not yet, after the PoC, I'll slowly reimplement them in c.
orignal
you need transports, you need netdb, you need crypto
radakayot
oh sorry. you are right.
radakayot
33 total.
orignal
33 sounds more resonable
radakayot
sent you the file list.
radakayot
I patched some methods to make it more suitable for my needs. it's all automatic.
radakayot
also removed meshnet support unfortnately.
radakayot
i'm hoping you are not planning to make drastic changes to the libi2pd implementation for the next 3 months :)
radakayot
but orignal, without your efforts, I couldn't even dream to make a PoC in this short period of time. so thank you again.
radakayot
I may have some questions regarding the implementation differences between i2p java and i2pd.
radakayot
is there any document that I can find the implementation differences between two projects? (only i2np and i2cp is enough)
dr|z3d
I don't think anyone's written up the differences.
radakayot
from what i've seen gost support, floodfill handling and congestion controls are different.
radakayot
my goal is to be 100% compatible with the i2p java project and specs in the future, that's why I'm asking.
dr|z3d
compatiblity is one thing, feature support is entirely different.
radakayot
first goal is 1 to 1 compatibility. including ciphers.
dr|z3d
if you're coding in C, i2pd is a fine reference point. there are differences in implementation, but compatiblity isn't an issue. the only things that aren't compatible are the gost crypto and support for yggdrasil, which are both exclusive to i2pd.
radakayot
as for the features, i don't have any plans to support sam, tunnels, addressbook, proxy etc.
radakayot
dr|z3d: I'll leave the gost support for the sake of fsb. :)
dr|z3d
don't get orignal started :)
radakayot
I see his point actually, Occam's razor.
radakayot
ah also, i really want to ask something to you orignal. do you have any testnet setup you can share that i can quickly get it up?
orignal
you can drop gost. it's not used anyway
orignal
no we don't have a testnet
dr|z3d
are you planning to drop gost, orignal?
orignal
but it can be configured easily
orignal
no, why should I
dr|z3d
<orignal> you can drop gost. it's not used anyway
dr|z3d
your words.
orignal
well you can still set signaturetype=9 or 10
orignal
nobody uses it but still can be used
dr|z3d
if no one's using it, why not drop it, reduces maintenance burden, streamlines codebase.
orignal
it's just slow vs. EdDSA
orignal
myabe people still use it, idk
dr|z3d
you could sunset it, give people advanced warning. up to you.
orignal
goiing to make it configurable
orignal
but never have time for it