@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest19353
Irc2PGuest22478
Irc2PGuest48042
Irc2PGuest64530
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
hagen_
khb
not_bob_afk
plap
poriori
profetikla
r3med1tz
rapidash
shiver_1
solidx66
tr
u5657
uop23ip
w8rabbit
weko_
x74a6
eyedeekay
dr|zed sorry I missed it in the scrollback the first time I looked, but to reseed-tools reseed as an onion is just a flag, you can activate it and it will automatically host a reseed on onion or TLS endpoints(technically it can also do in-I2P too but what's the point?) but outside of a few very narrowly useful things I haven't found anyplace it really offers much
eyedeekay
In fact anything that implements a net.Listener, as long as it's reachable, can be plugged in as a reseed in reseed-tools
eyedeekay
Onion mode also has a drawback, in it's present form IIRC I give all onion reseeders the same bundle to prevent the onion endpoint from being a convenient way to scrape
eyedeekay
It might be useful for a privacy-focused OS that uses Tor for all non-I2P connections, or for running a private reseed server for a single project
eyedeekay
Reseed-over-Onion was useful on some US university networks where reseeds appeared blocked but Tor was able to bootstrap and I2P connections worked, similar environments probably exist elsewhere
eyedeekay
But all told it's software without much application yet, it stays in reseed-tools because it's simple to leave it there
dr|z3d
> eyedeekay: yeah, I'm thinking of something in the console that a) looks for a running tor/tor browser instance if there are .onion reseed hosts configured and b) falls back to using any detected instance in the event a default, new install reseed fails.
eyedeekay
I've got a branch that does pretty close to that
dr|z3d
no need for knobs and sliders, should just handle that in the background.
dr|z3d
for a) all that's required is an .onion address in the list of hosts, b) doesn't need anything except a log entry.
eyedeekay
It does: i2pgit.org/idk/i2p.i2p/-/compare/master...dynamic-onion-reseeds?from_project_id=8&straight=false
eyedeekay
Yup, that's what it does, although there might be a simpler/better way to do it
dr|z3d
don't like the idea of automatically setting the proxy.
dr|z3d
I mean, if the user wants to use Tor over socks for their reseeding, let them do it manually. otherwise, leave the proxy config alone and just proxy out for .onion reseed packages without changing the config.
dr|z3d
but otherwise, you're on the right track.
eyedeekay
Yeah I think the behavior you're describing was my goal and changing the proxy settings was just how I did it at the time, if I revisit that I can probably change how that works
dr|z3d
basically, look for .onion hosts in the reseed list, if found, check for a suitable tor proxy on 9050 or 9051. and then just treat the .onion host as another possible link to use randomly.
dr|z3d
*9050 or 9150 sorry.
dr|z3d
if otoh, the only reseed link that works is the .onion link, _then_ set the proxy to the discovered tor socks proxy.