@eyedeekay
&eche|on
&kytv
+R4SAS
+RN
+T3s|4
+acetone
+dr|z3d
+orignal
+postman
+weko
An0nm0n
Arch
FreefallHeavens
Gid
Irc2PGuest1893
Irc2PGuest3088
Irc2PGuest32938
Irc2PGuest4253
Irc2PGuest8259
Leopold
Minogami
Onn4l7h
Sleepy
Soni
T3s|4_
Teeed
aargh1
admin
anon
apt0110
b3t4f4c3__
cheddah
eyedeekay_bnc
idk
itsjustme
j6
limak
not_bob_afk
polistern
poriori
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
u5657
user101
wodencafe
x74a6
eyedeekay
We would need webrtc and websocket transports but there could be crazier ideas
dr|z3d
what's the proposition, eyedeekay?
dr|z3d
re web sockets, perhaps the bidirectional http tunnel def could be upgraded.
dr|z3d
upgraded/cloned and repurposed
zzz
eyedeekay, how did you pull in the translations on June 29 for 2.3.0? Because they contain fuzzies, which shouldn't have happened. Did you use the v3 tx tool?
zzz
actually, you couldn't have, because the .tx/config file hadn't been migrated
zzz
so what did you do?
zzz
could have sworn you told me you got the v3 client working; maybe you did on www, but there's no evidence you did on i2p.i2p, and the config file was broken until I fixed it today
dr|z3d
watch out for the fuzzies, they kill the vibe :)
zzz
I think "how did we get here?" is now my permanent vibe
dr|z3d
lol
RN
😈
zzz
anyway, by reverting the mess that the tx migrate tool did to our config, I knocked 1500 lines out of the diff-from-release
RN
wow
eyedeekay
Didn't see most of this convo until I checked major, I'll start with some answers, then have some questions
eyedeekay
When I did the i2p.i2p release the v2 transifex tool still worked. By the time I did the i2p.android.base release the v2 transifex tool had stopped working and I couldn't update those translations, which forced me to migrate those in the middle of the release
zzz
v2 tx pull never returned fuzzies before afaik, you sure you used it for the 2.3.0 release?
zzz
I thought you never got v2 tx working, you had problems for several months early this year
zzz
and your fix was to move to v3. but maybe I'm misremembering
eyedeekay
I got v2 tx working successfully a few months before the release but it broke in the middle of the release, I remember because I was really blindsided, it's just possible that I might have mixed up the output of the builds but I think I uploaded i2p.i2p before I moved on to the rest of the projects
zzz
ok, I guess the fuzzies are a mystery then. I'll keep an eye out for them next time
zzz
there's a lot of diff in the 2.3.0 checkin, not just the fuzzies, which maked me think it wasn't via tx
zzz
but I was right it wasn't v3
eyedeekay
I might have accidentally used the v3 transifex tool on it and ended up with the fuzzies, the simplest answer is that I did that and failed to check in the migrated config
eyedeekay
But there was a long time between i2p.i2p and i2p.android.base in part because of this it just seems the chance to mix up the build outputs of i2p.i2p up was narrow
zzz
ok, well that's a completely different theory
zzz
I pulled today and didn't get fuzzies
zzz
but whatever you did check in for .tx/config didn't work for me, so I don't know if it worked for you or you just reran the migrate tool which is busted I fixed it today.
eyedeekay
It worked for me with `TX Client, version=1.6.7` which I installed with `go install`
zzz
hmph. I'm on the latest 1.6.10
eyedeekay
I'll update, neglectful, my bad
eyedeekay
As long as it works and the diff is smaller, thank you for fixing it zzz
zzz
nah, just a lot of variables makes it hard to diagnose what happened, and it ultimately doesn't matter
zzz
the migrate just scrambled the carefully alphabetized trans.xx lines and tossed all my comments over 15 years, it just irked me
zzz
not your fault