Vort
Vort
> My "solution" has been showing peer_id in place of ip:port to make some sense. I think that putting non-addresses into address column is inappropriate. For me it is better...
> Are those destination addresses base32? (it looks like the .b32 part of the address might indicate that). Does that mean they are 32 byte keys? _"I2P uses 52 characters...
Not sure what place are you talking about, but full base64 keys are needed for interactions with SAM.
> That's not what the documentation says `STREAM ACCEPT` uses full key: _"SAM bridge sends the client a ASCII line containing the base64 public destination key of the requesting peer"_...
Ok, I agree that it may be possible. However I'm not sure which approach will be faster. 1. Frequent "string handling and heap allocations" vs occasional SHA256. 2. Making base32...
I asked @orignal and he said that storing of base32 addresses is good solution.
7e3157b162b644e8624aaea1057fb712052c4761 commit have related changes. Can anyone check if it fixes this problem?
I think main question here is how hard to implement autodetection for `ipv4` and `ipv6`. Enabling `ipv6` when user have no IPv6 available is bad decision I think.
Because generator didn't work well and @orignal have no time and enthusiasm to fix it.
I heard that generator for GPUs exists, but I did not tried it and don't know its name and location.