eche|off
<i2puser> I have the deb.i2p2.de repo, and apt tells me its certificate expired. So I can't check for updates.
eche|off
maybe, idk_afk have a look
dr|z3d
zzz: if you're in touch with the stormycloud tor exit guy, see if you can get him on irc. I don't mind helping him with some suggestions re outproxy connfiguration, but I don't want to reveal operational info on the forum.
dr|z3d
exposing the stack I'm using on zzz.i2p sounds like an invitation for the skiddies to come and play.
zzz
its not a fast RTT, already been weeks
zzz
ok. I don't feel any need to chase them, when they're ready they will ask
zzz
if you want to reach out sooner, twitter DM or I'm sure you could find other contact info on their site
zzz
generic info like 'privoxy suxx', please post in the thread
dr|z3d
re mitigations, I wonder if the ff's can be made more tolerant of multihomed leasesets, perhaps by having the sending router include a "I'm multihomed" flag with the publication which then causes the ff's to throttle less aggressively.
dr|z3d
ok, so 20 routers @ 0 hops on a single dest should be doable then.
zzz
there's nothing wrong with throttling, it doesn't matter if the flooded-to ffs have a different LS 20 seconds older
zzz
or, perhaps time to bring back garlic farm
zzz
i think the ff will still store locally if over the limit, it just won't flood
dr|z3d
ok, so if that's the case, then 20 multihomes on 0 hops sounds like it shouldn't cause any issues.
RN
When adding a b32 or b64 to the Restricted Access list, can a comment be added after the dest by prefixing the comment with # or similar?
RN
This would be helpful to remind me why I blocked each one
RN
It would be even nicer if I could block based on the requested URL as the requesting dest can change
dr|z3d
no comments, just the dests.
RN
:(
RN
feature request?
dr|z3d
that would be a job for the tunnel filter, url blocking.
RN
I wouldn't expect it to be too hard to ignore the rest of the line once .i2p has been parsed