Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support i2p #1320

Open
ghbjklhv opened this issue Jun 13, 2019 · 2 comments
Open

[Feature] Support i2p #1320

ghbjklhv opened this issue Jun 13, 2019 · 2 comments

Comments

@ghbjklhv
Copy link

ghbjklhv commented Jun 13, 2019

Objective: Implement and Support i2p in Matrix and Riot.im
Description: Explore the possibility of using Matrix over i2p.
Would non-i2p users be able to still communicate? Would you need to craft a bridge?
Why?: Many reasons, mainly for privacy and security but also to support decentralized communications.


Want to support this issue? Post a bounty on it! We accept bounties via BountySource.

Bountysource

@cyphar
Copy link

cyphar commented Jun 14, 2019

This is (at least somewhat) related to matrix-org/synapse#5152 -- the basic problem is that right now there isn't a way to proxy synapse federation requests (from what I can tell that might even be a Twisted issue). We also will probably need to have a way to force a room to only be join-able by anonymous servers (like we currently can block non-local users from joining a room). We'd also need to get a large number of servers to proxy (at the very least) .onion services over Tor in order to make sure that the .onion homeservers would be able to get events.

On the client-side there shouldn't be too many issues (you can always just open the client in Tor Browser or the I2P equivalent).

@Mikaela
Copy link

Mikaela commented May 8, 2023

Also related to #200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants