&zzz
+R4SAS
+RN_
+T3s|4
+acetone
+mareki2p
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Daddy_I2P
Irc2PGuest35412
NiceBoat
Onn4l7h
Over1
Sisyphus
T3s|4_
Teeed
Zapek
aargh4
ahiru
b3t4f4c3___
duanin2
marek
n2_
not_bob_afk2
o3d3
poriori
profetikla
r00tobo
sahil
solidx66
uop23ip
urist_
x74a6
zelgomer
orignal
I'm fine
zzz
> eyedeekay, dr|z3d, I propose Tues. Feb. 10, 8 PM UTC, for the Proposal 169 PQ transports review. Let me know if that works, or suggest an alternate date
orignal
ipv4 is back at 2RRY
orignal
so NTCP2-PQ is full functional there if someone wants to test
orignal
what about rust(y) guy?
zzz
I'll invite him via email
orignal
my impresson is that nobody else care
orignal
s
zzz
sure, but I'll announce in a few places and invite everybody
zzz
I finished all the updates to the proposal, up at i2p-projekt.i2p/spec/proposals/169
orignal
SSU2?
zzz
yes, I updated both transports. We can review both if we have time
orignal
how did you resolse this issue with Bob's hash?
zzz
as you proposed, and I documented on zzz.i2p/topics/3697
orignal
let me see
orignal
this MixHash is for ver 3 or 4 only?
zzz
yes, that was your proposal
orignal
nice
dr|z3d
10-4, zzz, re meeting.
zzz
thanks drz
zzz
orignal, I plan to start working on SSU2 next month, target March or April for testing
zzz
orignal, if you missed it, check your email for new reseeds
eyedeekay
Feb 10 8UTC works for me, I will go over the changes to the proposal by then, not sure where I will be on PQ in Go by then but probably not much farther than I am now, still working on clients
zzz
thanks. implementation is not a requirement for review, normally thats the order we do it ))
zzz
I'll email emissary
zzz
fun fact: this will be the 4th review of 169, the first was March 18th
orignal
no I didn't miss just didn't have time
orignal
eyedeekay what PQ lib do you use in Go?
zzz
I dont think he's started yet, he's working on i2cp
orignal
zzz, read your e-mail about certs
orignal
looks the same guy )))
eyedeekay
orignal I'm using github.com/cloudflare/circl for now, will be switching to go std when go std gets it
eyedeekay
I have to do the hybrid noise stuff myself though, I don't think any available upstream in Go is going to do that for me