i2p general thread - general thread about the i2p network

[Fresh Meat]

Only internal I2P communications are end-to-end. To me it's unclear if that's a feature that is done automatically on your end with some sort of trick on your end and the recipient/sender end or if the service provider like Postman does it automatically with your messages like how Proton does it.

Good news: specification 167 for peer to peer I2P e-mail is in the works and nearing completion, thanks to zzz's work.
http://zzz.i2p/topics/3641-p2p-email-proposal [b32, archive attached]
http://git.idk.i2p/zzz/i2p.i2p/src/branch/prop167-i2cp/ [b32, clearnet]



I think this specification is supposed to be a second attempt at I2P-Bote, since that was abandoned 7 years ago. For those not in the know, I2P-Bote was a plugin for I2P that allowed direct sharing of e-mail through DHT, automatically encrypting and signing them. Someone tried reviving the project [a], and the fork got abandoned the same way shortly after.
http://git.idk.i2p/I2P_Developers/i2p.i2p-bote [b32, clearnet]
http://zzz.i2p/topics/2853-rip-bote [b32, archive attached]
https://github.com/i2p/i2p.i2p-bote

HTML archives made using SingleFile, contain no scripts.

---

As I was bemoaning the lack of a web archival service on I2P while writing this very post, I decided to actually search deeper and see if there was any real alternative for archiving eepsites, and, I found out an actual archival service appeared yesterday, under the address "archiver.i2p" [b32]

It has a lot of limitations [b32], however. Mainly the fact that there is a forceful 30 day grace period between archival of the same specific URL, and the fact that only 2000 pages can be saved per domain.

I also wasn't able to find any contact information whatsoever, no e-mail nor IRC contact.