I2P+ is a lot more aggressive when dealing with potentially hostile peers, which can often result in less transit (participating) traffic, and is also pretty selective about low-bandwidth peers that appear to be running outdated versions. It's also a lot more selective about the peers it chooses to ...

Latest revision, based on feedback (untested). #!/bin/sh # Requirements (Linux): curl, grep, cut, head, printf, tail, date # Optional requirements for desktop notification: notify-send # I2PSnark (embedded or standalone) # Initial idea by Titus # Shell script conversion by Phithue7 # Error handling,...

I've added some basic error handling, an optional argument --enable-notifications, removed any html tags from the notification and cleaned up the code: #!/bin/sh # Requirements (Linux): curl, grep, cut, head, printf, tail, date # Optional requirements for desktop notification: notify-send # I2PSnark...

Most routers I'm connecting to are shown as being from an "unknown" country. When my router reaches over 1000 known peers, it starts to have problems connecting to them lately and I have to restart. I mainly use I2P+ if that matters. However I also see a lot of sites are down regardless o...

An issue with 2.5.2+ has been identified and fixed in the latest release and dev updates and the installer on http://skank.i2p/ and http://i2pplus.github.io/. The issue manifests as a gradual loss of peer connections and floodfills. This was due to the temporary blocking of peers sending unsolicited...

I have the router version (2.3.0-117+) that I am trying to connect the IRC servers. Unfortunately, it cannot connect to the servers possibly need a fix for that. Is it possible to modify the settings? Sure you can modify the servers, but you should first check your addressbook, however, and make su...