I'm getting back into the swing of working on @i2p proposals (for changing the network specifications), starting with editing and expanding prop 125 which is aimed at improving network performance. Comments welcome!
https://geti2p.net/spec/proposals/125-obep-to-one-of-many-tunnels
Hopefully I'll manage to bash through several more proposals from my backlog this weekend ๐
I2P April Dev Meeting: https://geti2p.net/en/meetings/258 Discussions about I2P Summer Dev! Focus on optimization - (LS2, newer E2E encryption, massive multihoming).
I've figured out how I can set up an instance with an @i2p address. The underlying protocol currently uses the host from username@host.url to handle federation, but the underlying WebFinger RFC only has a SHOULD for that, so in theory we could have user@something.i2p with the backend knowing how to get there out-of-band.
Progress! I have a Mastodon instance with registration working for mail.i2p email addresses! Now figuring out how to hack around the SSL checks for @i2p without disabling SSL for clearnet. I'm probably going to have to learn some Ruby and Rails ๐
This is the official account for i2p https://geti2p.net/en/