Ye sure we can test :)

Don't. It's not good for the network and it's not good for the people who run exit nodes. Just don't do it.

Maybe I should try it out when I have something I need again 🤔

Sheesh, please bin the Nazis and racists into their own category, instead of "Adult/NSFW." Nazis are real boner-killers.

Ha, yeah... I wasn't quite for sure where to put them. But I figured labeling them NSFW was appropriate other than adding them under personal sites or services.

I'm not entirely sure, so but I dropped the link to this thread in IRC so perhaps you'll get an answer soon.

Sheesh, please bin the Nazis and racists into their own category, instead of "Adult/NSFW." Nazis are real boner-killers.

Yeah, it's similar. Though, it's just a file sharing program. Nothing amazing at this point. But, it does work and it's i2p specific. It's likely got the most files of any of the i2p file sharing programs out there.

It's a server on a shared 1Gbps port, but the output depends on the I2P network demand and how congested the port is with neighbors.

Right now I'm averaging about 13Mb/s constantly, which in the last 12 hours or so the minimum demand was 8Mb/s and the max being 20Mb/s.

But if I wget a speedtest file...

$ wget -O /dev/null http://mirror.leaseweb.com/speedtest/1000mb.bin 
--2020-12-20 10:40:43-- http://mirror.leaseweb.com/speedtest/1000mb.bin
Resolving mirror.leaseweb.com (mirror.leaseweb.com)... 209.58.135.187
Connecting to mirror.leaseweb.com (mirror.leaseweb.com)|209.58.135.187|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1000000000 (954M) [application/octet-stream]
Saving to: '/dev/null'

/dev/null 100%[============================================================================>] 953.67M 46.8MB/s in 22s 

2020-12-20 10:41:06 (42.4 MB/s) - '/dev/null' saved [1000000000/1000000000]

Then I'm getting about 47Mb/s down while the router is still running/serving traffic.

Old server was 'faster' but I had monthly data caps and I never took advantage of the faster network anyway, I2P was never demanding enough to need to serve that much traffic at once:

wget -O /dev/null http://mirror.leaseweb.com/speedtest/1000mb.bin
--2020-12-20 10:44:16-- http://mirror.leaseweb.com/speedtest/1000mb.bin
Resolving mirror.leaseweb.com (mirror.leaseweb.com)... 209.58.135.187
Connecting to mirror.leaseweb.com (mirror.leaseweb.com)|209.58.135.187|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1000000000 (954M) [application/octet-stream]
Saving to: ‘/dev/null’

/dev/null 100%[============================================================================>] 953.67M 60.1MB/s in 12s 

2020-12-20 10:44:28 (82.1 MB/s) - ‘/dev/null’ saved [1000000000/1000000000]

What speed do you get?

That did the trick, thanks bud.

Now on a better (less congested) network with no monthly data-cap.

Those directories are non-existent. Anything I2P related is all under /home/user/i2p/

I'll try the method /u/z3d mentioned and report back.

If you're not running a repo or .deb installed version of I2P, or you're running I2P+, backing up your settings is as simple as copying the ~/.i2p/ directory to the new $HOME location, and if necessary, chowning it to ensure it's owned by the user account running I2P/I2P+ on the new server.

You can either move ~/.i2p/ to your home directory before you run I2P/I2P+ for the first time, or, if you've already run I2P/I2P+, delete the existing ~/.i2p/ directory and copy your backup there. All existing configs should be restored without issue.

Thanks, I'll give that a whirl.

You're probably running Ubuntu or Debian, right?

I'd shutdown the node and simply tar /var/lib/i2p/, install I2P on the new device, make sure it's off, rm -rf /var/lib/i2p, untar your backup archive and chown -R i2psvc /var/lib/i2p (change the owner to the i2p service). Then you can start i2p up again.

Never done that before, but I think that's they only state i2p stores.

Does it bring back LimeWire, Napster, Kazaa, WinMX, etc. vibes?

Are there any bugs you've encountered?

You can also use putty to SSH tunnel :)

Ha! Good call. I'll update it now.

I'd clarify that homosexualchan.i2p was spoofed by someone as a joke, and real domain of that board is 2ch.i2p.

Nice collection of links here for people who use I2P. Very helpful.

I'll keep this pinned for a few days.

I've used the plugin and standalone. Both do what they say they do. Downloads are slow. But, that's to be expected.

As an I2P plugin.

Do you use standalone or as I2P plugin?

I guess since somebody has to generate and seed the bundle and for the time being, this is a scheduled rather than automatic task yes, this is not a purely client side solution yet. In a realistic future where we are able to do a similar thing, but with a git-transport that talks to the torrent client directly rather than by downloading a periodically generated bundle manually, the person seeding the periodic bundle could become much less important, assuming that most of the people seeding i2p.i2p through this hypothetical gittorrent-like system are updating to the latest code pretty frequently so that they're usually seeding pretty much the latest version. Swarm Merging would also be a huge help here I think. Then the only centalized(hypothetically) point you would have left is whatever you use to provide the human-readable alias you use to fetch the latest version of the corresponding(i2p.i2p) torrent. This is the part I don't quite get yet, I guess what other people(the gittorrent folks) have done is use a blockchain to distribute a list of infohashes associated with a given name that's registered by performing some kind of transaction? Not sure. Haven't had time to read up on that yet and every time somebody says "applied blockchain" people groan and say "are you sure?" I'm no different.

So this workaround is not client-side only, a little pity.