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.

Sign up for GitHub

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

Jump to bottom

Fix Tor #2

Open

chrisguida opened this issue Apr 16, 2022 · 1 comment

Assignees

Owner

chrisguida commented Apr 16, 2022

No description provided.

chrisguida self-assigned this

MattDHill mentioned this issue

[Initial]: IPFS v0.15.0 Start9Labs/service-pipeline#3

Closed

4 tasks

Owner Author

chrisguida commented Sep 8, 2022 •

edited

Loading

This doesn't seem like it will be tractable right now. IPFS appears to have a love-hate relationship with Tor

epic https://flyingzumwalt.gitbooks.io/decentralized-web-primer/content/avenues-for-access/lessons/tor-transport.html
and apparently tor gateways are a thing too https://flyingzumwalt.gitbooks.io/decentralized-web-primer/content/avenues-for-access/lessons/tor-gateways.html
uh oh ipfs/notes#37 (comment)
most recent state of things: ipfs/notes#37 (comment)
anyway, people using this are just gonna have to be ok with their home IPs being linked to files they upload/pin
https://github.com/protocol/research#private-retrieval
grant offer to create a transport that is both faster and more private than Tor (!!) https://research.protocol.ai/blog/2022/announcing-rfp-014-the-one-with-private-retrieval/

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