[Feature] Built in I2p Support

[asddsaz]

Feature: The ability for users to access LBRY with I2p

Why? To help evade censorship in countries like China.

Acceptance Criteria

Definition of Done

• Tested against acceptance criteria
• Tested against the assumptions of the user story
• The project builds without errors
• Unit tests are written and passing
• Tests on devices/browsers listed in the issue have passed
• QA performed & issues resolved
• Refactoring completed
• Any configuration or build changes documented
• Documentation updated
• Peer Code Review performed

[tzarebczan]

@asddsaz thanks for opening this issue! I don't think we'll be tackling this anytime soon as the goal of LBRY is to build upon current/popular internet infrastructure, but if there are any community members that would like to take this one, we'll leave this issue open.

[geekodour]

@tzarebczan @asddsaz can you give me any idea on where would be a good idea to get started with this. I am familiar with network programming in C but that's all.

[tzarebczan]

@geekodour this may not be a good fit for you as this codebase is in python, but this would must likely require some good understanding of how our current P2P layer works as well as I2P.

[eukreign]

We're not planning to work on this anytime soon. It sounds interesting and useful and if someone wants to implement this we'd be supportive. We're trying to cleanup our backlog so I'm closing the issue for now.

[asddsaz]

@eukreign @tzarebczan If at all possible, I would appreciate keeping this issue open for future discussion.

[asddsaz]

@geekodour I2p has a page on BitTorrent: https://geti2p.net/en/docs/applications/bittorrent
I would also look into i2p.socket: https://github.com/majestrate/i2p.socket

[tzarebczan]

I think it was closed because we are still making the current DHT implementation efficient and error proof, so we won't be starting one for another protocol. Remind us again next year :)

[kodxana]

I think it was closed because we are still making the current DHT implementation efficient and error proof, so we won't be starting one for another protocol. Remind us again next year :)

Remind you next next year :)