~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Xeha
+bak83
+cancername
+cumlord
+hk
+poriori
+profetikla
+uop23ip
Arch
DeltaOreo
FreeRider
Irc2PGuest15271
Irc2PGuest28511
Irc2PGuest64530
Meow
Nausicaa
Onn4l7h
Onn4|7h
Over
acetone_
anon4
anu3
boonst
mareki2pb
not_bob
plap
shiver_1
simprelay
solidx66
thetia
u5657
weko_
KernelHawk
Thanks!
dr|z3d
welcome to #saltr!
not_bob
welcome to #saltr!
dr|z3d
KernelHawk: you looking to improve snark's performance, or just curious how it all functions?
KernelHawk
My main goal was to understand i2psnark's DHT and PEX implementations so that they could be adapted for libtorrent for better compatibility.
KernelHawk
Thinking it would help push more peoples towards torrenting over I2P.
dr|z3d
well, if you have question's, zzz's the snark DHT/PEX expert around here.
dr|z3d
*questions
dr|z3d
afaik, libtorrent's had a fair bit of work done lately to make it compatible (again) with i2p.
KernelHawk
I see they use the SAM protocol, which works, but it is no where near the torrenting efficiency of i2psnark.
KernelHawk
I will do more digging before I try and bother you guys. I do not want to distract you from the main developments.
dr|z3d
yeah, snark uses i2cp. not sure why SAM's slower, but I've noticed it's slow in i2pchat.
zzz
KernelHawk, i2p-projekt.i2p/en/docs/applications/bittorrent should be all you need to know
KernelHawk
zzz: thanks. I will analyze the docs and the code.
zzz
ok, but like I said, the docs should be enough
KernelHawk
zzz: say I wanted to send raw requests to a tracker or a DHT peer, would using a SAM library with raw data be okay?
dr|z3d
tldr: to enable ipv6 for i2p without impacting your firewall, disable your firewall.
dr|z3d
that's google's bard AI offering excellent help there.
zzz
KernelHawk, PEX is super-easy and DHT is very much not
zzz
as dr|z3d says, snark is I2CP and libtorrent is SAM, so you won't learn how to send/recevie datagrams by looking at snark
zzz
"raw requests" == UDP == datagrams == SAM 3.3 required. But no i2p trackers support datagrams, you'd use it for DHT only
zzz
icymi
zzz
<zzz> KernelHawk, PEX is super-easy and DHT is very much not
zzz
<zzz> as dr|z3d says, snark is I2CP and libtorrent is SAM, so you won't learn how to send/recevie datagrams by looking at snark
zzz
<zzz> "raw requests" == UDP == datagrams == SAM 3.3 required. But no i2p trackers support datagrams, you'd use it for DHT only
dr|z3d
Blinded message
dr|z3d
or that. :)
KernelHawk
learning curve haha
dr|z3d
release and ghost are your nickserv friends.
dr|z3d
Blinded message
KernelHawk
zzz: thanks for that. That makes sense. Forgot that I2CP is the protocol used for snark
KernelHawk
Does release mean logout?
KernelHawk
nvm, the help cmd told me
KernelHawk
Appreciate the info!
zzz
KernelHawk, another workaround for not supporting DHT is to simply always announce to the known opentracker, that's about 1000x easier
KernelHawk
zzz: yeah that does sound much easier honestly.
zzz
here's your DHT issue with a link to the PEX issue I entered a while back: github.com/arvidn/libtorrent/issues/7408
zzz
if you're going to work on it you may wish to let people know there
KernelHawk
Sounds good
KernelHawk
Do you have a backup of the zzz.i2p forums at all? I see there is a reference to your forums (http://zzz.i2p/topics/812) on the bottom of i2p-projekt.i2p/en/docs/applications/bittorrent
zzz
it's down right now but it may come back
KernelHawk
No worries. As long as the information is somewhere.
dr|z3d
re farsi/persian, the reason I mentioned that before, zzz, is because we now have quite a sizeable Iranian contingent in the netdb.
dr|z3d
locally, it's only bested by the US routers in terms of numbers, larger than the Russian contingent.