Recent comments in /f/I2P

not_bob wrote

I would also suggest that users add my hosts.txt file.

http://notbob.i2p/hosts.txt

Or if you are feeling brave I also have a list of every host I have ever found.

http://notbob.i2p/hosts-all.txt

Note that these are automaticity generated from ongoing scans of the network and only include alive hosts. If a host has been dead too long it gets removed from the list.

You can see the full details at http://notbob.i2p

3

Rambler OP wrote (edited )

Ah, hell. Even the only outproxy worth a damn isn't in the default subscription list: purokishi.i2p

I've been advertising this site (ramble.i2p) and getting people to join and check out the I2P network without realizing they can't access this site and suggesting purokishi.i2p as their outproxy when they complain about the slow false.i2p default outproxy without realizing neither are accessible out of the box.

Glad I did a default vanilla install to test something out as a brand new user and realized this.

Is there a reason why you have to do register your domain in different locations to be on different subscription list (and wait days) and why the default one can't just include everything by default? Seems like it'd be a lot more user friendly that way, considering you can spin up a .onion domain in seconds, the same with a Loki or Yggdrasil address.

I like I2P a lot and want to see it grow but I didn't quite realize the shortcomings of the default, vanilla product.

The vanilla help/documentation states:

Speaking of address book updates, this would be a good time to add some more addressbooks to your own subscription list. Go to your Subscriptions Configuration page and add one or more for an automatically updated list of new hosts:

http://stats.i2p/cgi-bin/newhosts.txt (stats.i2p)
http://no.i2p/export/alive-hosts.txt (no.i2p)

Why not just include them by default instead of recommending them? That would add functionality and access out of the box.

1

z3d wrote

The short answer is "you don't".

However, if you add a clearnet magnet link or infohash to I2PSnark, you may be surprised to find it downloads if enough BiglyBT or Azureus clients are sharing it over I2P and clearnet. The bigger the torrent swarm, the more chance there's an I2P-enabled client or 2 in there to download from.

2

guestofhonor wrote

I tried it a few times and was disappointed. I was trying to create future addresses, export them and get the message later. Paste bin! Even under the best circumstances did not work for me. I use PyBitmessage, Retroshare, and other you did not hear about anyway (DaveMail).

2

Rambler OP wrote

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.

2

Rambler OP wrote

Reply to comment by XANA in New I2P router is going strong. by Rambler

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]
1

z3d wrote (edited )

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.

2

abralelie wrote

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.

2