@Xeha
@orignal
Arch
Danny
Irc2PGuest21863
Irc2PGuest27222
Irc2PGuest39482
Leopold
Meow
R4SAS
RN
RN_
StormyCloud
acetone
aeiou
aisle1
ardu
aside
b3t4f4c3__
eyedeekay
hagen
hk
mareki2p
poriori
qend-irc2p
r00tobo_BNC
radakayot_
rapidash
semantica
shiver_
thetia
u5657
weko
woodwose
x74a6
yeti
aisle
I'm unclear if this belongs in this channel or #i2p-dev, but I'm looking into the viability of using I2P as a privacy layer for a multiplayer game I'm developing. To do this, I would need to create single-hop tunnels with exclusively low-latency routers (ideally those in close geographic proximity to the user). Is this possible to do via API? After reading the reference client and i2pd documentation, I could not d
aisle
ble of controlling tunnel creation to such a degree.
orignal
explicitPeers in tunnel config
aisle
I noticed that under the I2CP controls, but I couldn't find anything in the documentation that would let me get a list of known routers or their latency. Would I need to modify the daemon itself?
orignal
there is no such thing
orignal
if you wish you should implement own profiling
aisle
I wasn't aware profiling methodology could be changed piecemeal, I'll look into that immediately.
orignal
nobody uses "low-latency routers" because it's a risk for anonymity
aisle
Thankfully only weak anonymity is required for my purposes. Large scale deanonymization attacks are out of scope for most multiplayer games, but I'm hoping that I can accomplish this without straying too far from the beaten path so the routers used for the game can still benefit the network as a whole.
orignal
then make tunnels of zero length
orignal
if you don't need anonymity
aisle
Anonymity is still required, just weak. The threat model is protecting against other players, not nation states.