IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2023/03/15
mesh wow so aws has taken down the whole web
mesh so much for a decentralized, nuclear-resilient, distributed web
RN must be regional
mesh everything's down and not coming back any time soon
mesh RN: can you reach say reddit.com?
RN not seeing issues here in [REDACTED]
mesh oh that's interesting, reddit is back up in the US
RN yep
RN did you look on downdetector mesh ?
mesh I mean it was definitely down but it seems the problem is now restricted to the east side (of the planet)
mesh downdetector doesn't really mean anything. The only downdetector I trust is of course the one on my machine
RN I find it useful to determine if it is just my setup or a bigger issue.
mesh good point
dr|z3d eyedeekay: re issue #393, there's a reason 6 digits is max in the b/w input fields.
dr|z3d without modifications to the bloom filters, the max bandwidth canon can handle is 128Mb/s iirc.
dr|z3d set 999999KB share and you'll find the actual share value is much lower.
dr|z3d give i2p+ 8 cores and 4GB ram, it'll push 1Gb/s.
eyedeekay I see. Well I probably shouldn't be messing with the bloom filters yet so those will stay the same for a while.
dr|z3d no, you probably shouldn't :)
dr|z3d under normal circumstances, the max share b/w never gets reached. only seen more than that when an attack's in full swing.
dr|z3d it may be in the future more than 128Mb/s is routine on a fast router, but we're not there yet.