Leaking what? DNS requests, external links? Can you be more specific, or is it just your software saying it's leaking
but not giving you any information?
Posted on: def3.i2p

>"It would not be the first time when Def or me (probably you 2) were taken." When was Def taken?

if this is about def.i2p (the first of my nodes), it was not "taken", but i lost the keys (long story...). it was replaced by def2/3/4, 2 and 3 running the same software as the first one (fudforum).

the js on skank.i2p seems to be a bit annoying for me, as it contradicts in some ways the use of darknets. that is my position anyway.

cheers

wed

Posted on def4.i2p

picture display does not work with xcf, shit...
this is the png

Posted on def4.i2p

Regarding DNS leaks, it sounds like your client is leaking
the DNS queries, not I2P+ (or I2P). Check that your client
is configured to proxy DNS requests over the proxy, not
locally.

In respect of skank.i2p, the ViewMTN service has optional
javascript components that shouldn't impair your use of the
site if disabled. The same complaint might equally be made
about this site, given that it links to 4 scripts.
Posted on: def2.i2p

>The same complaint might equally be made about this site, given that it links to 4 scripts.

oh shit, that is right. i always meant to patch those out, since they are harmless, but not needed for the site to function, and my opinion is as described above. but then this to do list got shuffled up somewhere...mumble

thanks for pointing this out, that will be taken care of.

cheers

wed

Posted on def4.i2p

>Regarding DNS leaks, it sounds like your client is leaking the DNS queries, not I2P+ (or I2P). Check that your client is configured to proxy DNS requests over the proxy, not locally.

as for this point, i agree that this would be an explanation.
could also be, that i2p+ triggers some alarms in cautious/paranoid evironments. guess it would have to be tested like already suggested...

Posted on def4.i2p

The other possibility regarding DNS leaks is that the
reseeding process is resolving the reseed hosts locally
(both in I2P and I2P+). To resolve, configure the reseed
process to use a proxy such as Tor on
http://127.0.0.1:7657/configreseed .. there's nothing
specific to I2P+ that should be causing DNS leaks that isn't
also an issue in upstream I2P.
Posted on: def2.i2p

no ragrets

Posted on: def3.i2p

$sha256sum poisoned_i2pupdate.zip
8c21b777f17950ddf77c0579dea0f8afb08cc6cd2e4e50856e863913c0b47acd poisoned_i2pupdate.zip

I rename it to keep track of it!
Size 5.0 MB (5021302 bytes)
Size on Disk 5.0 MB (5021696 bytes)
Posted on: def3.i2p

Latest version of I2P+ (0.9.38+) now available:

Highlights in this release:

* Implementation of global font to ensure console and webapps display
consistently on different browsers/OS's
* Add UI option in I2PSnark to display the add/create sections on all
pages when in multipage mode
* Add toggle full headers feature in Susimail (requires javascript)
* Add ransack.i2p metasearch engine to /home and searchbar
* Replace def2.i2p link on /home with def3.i2p to avoid multi-framed site
* Cosmetic improvements to all themes, both console and webapps

As always, the torrent and magnet links are available at:
http://skank.i2p/static/i2p+.html

Please note that I2P+ normally provides updates several times over the
course of a release period in order to introduce keen users to new
features as expeditiously as possible!

A list of changes specific to I2P+ is available at:
http://skank.i2p/static/changelog.txt

Enjoy responsibly!

--
I2P+ | From brutal to beautiful
Posted on: def3.i2p

>* Replace def2.i2p link on /home with def3.i2p to avoid multi-framed site

I never knew that you linked to def2...guess that explains the higher number of visitors on def2 vs def3. ok...
guess i will leave def3 running on fudforum after all...

Posted on def4

>to avoid multi-framed site

what is so bad about multiframes (serious question, i am not proficient in web design) ?

Posted on def4