i2p is different to tor in a variety of ways. One is that your device integrates with the network, so it is not secret from your device what your device is accessing at the moment. This is in contrast to tor whom have an official set of really-trustworthy-entry-nodes cooked in, so the device you are using changing is incidental since one hopes tor's trustworthy nodes are really super trustworthy.
Discussion
Loading...
Discussion
I think my proposition for i2p is to minimally consider it an extension to your private network. When I want to look at the staging version of my blog, or utility gophers inside my personal machines from inside a coffee shop, i2p is a meaningfully safer version of doing that
because instead of announcing my home address (my ip address) but hopefully installing a really good lock correctly,
I just participate as one of about 55 thousand other people using i2p and nothing else is public.
i2p is different to tor in a variety of ways. One is that your device integrates with the network, so it is not secret from your device what your device is accessing at the moment. This is in contrast to tor whom have an official set of really-trustworthy-entry-nodes cooked in, so the device you are using changing is incidental since one hopes tor's trustworthy nodes are really super trustworthy.
@screwlisp I just wish #i2p wasn’t created in #java . Look into #gnunet also , lots going on there.
@nixfreak well, how about C++ (i2pd's fully-compatible separate implementation of the standard / RFCs).
I wonder if embeddable common lisp could eat i2pd in an interesting way.
On the other hand, I think a lot of people use the java one, which has lots of applications (like their torrenting and mail) that i2pd does not try to reproduce. Iirc.
@nixfreak Mm, there's a reason I did not get all the way through writing my example of safely and privately connecting to myself from myself yesterday. Maybe tonight or tomorrow.
The fundamental thing one would want in general (i.e. a gopherhole) is an ed25519 encrypted LeaseSet2 tunnel of type server: https://docs.i2pd.website/en/latest/tutorials/blinded-addresse/
This is the one where you attach public keys to the port you host, and only people having the appropriate private key can even detect its presence (and access it).
Because there is the cost of helping i2p's network to trying to scrape i2p's network, i2p gets randomly DDoSed to slow it down instead of scraped like the clearweb.
There is also the attack that anyone (rival corporation, sordid journalist) can make a simple webpage that says naughty things on their computer anonymously public on i2p, and then disparage i2p for having such a naughty webpage technically available to the other i2p users.