The official community for Dread announcements, discussion, and feedback. Come post any bugs!
Only posts relating to this site in this subdread allowed! Posts here are manually reviewed before public posting!
by /u/Paris A · 17 votes · 7 months ago
-----BEGIN PGP SIGNED MESSAGE-----
And here I was going to just relax a bit, work on the recon update, and not worry too much. BUT NO. We can't have nice things.
I have been delaying the i2p endpoint announcement simply because my reliability with the i2p network has been... terrible is one word I'll use. It might because how I'm personally connecting into the i2p network or because of how the i2p network system is designed for dread (layers of i2p nodes to the core). I was figuring it out and also gathering information about how the i2p network handles different things. There is a chicken and an egg problem here with i2p. They need more people using their network. It is, from what I got from the IPs and bandwidth statistics on the distributed floodfill nodes, far smaller and far less resistant to Sybil attacks. They don't try to hide that fact (in their fantastic documentation) but it is still a problem. With scale there is a lot of promise here with the proper supports.
Dread will NEVER use any addressbook which can transparently MiTM attack you. It is very important to only visit using the base32 hostname. With that being said I'm going forward with the announcement to provide a hopefully more stable as time goes on i2p mirror.
This is Paris from Dread. As promised we now have an i2p mirror:
It is the biggest dicked i2p website yet. Guaranteed.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----