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

Anonymity + metadata protection #1

Open
0chroma opened this issue Jul 30, 2024 · 4 comments
Open

Anonymity + metadata protection #1

0chroma opened this issue Jul 30, 2024 · 4 comments
Assignees
Labels
future-work Not important now, maybe later though

Comments

@0chroma
Copy link
Owner

0chroma commented Jul 30, 2024

In the initial use case of tight-knit friend groups, knowing people's IPs should be ok. Eventually for more global, publicly accessible use cases, it will be required to have an option for anonymity at the cost of sync speed. People who are worried about metadata-centered data collection would also require this feature.

Potential options to investigate

Looking at other apps

Many other apps seem to just route over Tor/i2p. It probably would be way too slow, especially when low latency is required ie games + group calls. You also wouldn't be able to accept connections either. It's just not well optimized for decentralized multicast use cases like InductionDB unfortunately. Briar took this route, but I'm not sure how well it works.

Session uses their oxen routing network for messages, but still uses direct connections for calls at time of writing. In general I don't like the idea of involving cryptocurrencies, I'd rather the network be self-sustaining such that every InductionDB instance is contributing to the network. More info on oxen/lokinet here

Need to read about how Matrix is doing it still

Other places to investigate

There's a discussion on Freenet that is trying to figure out the same thing: freenet/freenet-core#813

Potential chart to investigate: https://bkil.gitlab.io/secuchart/

@0chroma
Copy link
Owner Author

0chroma commented Jul 30, 2024

Some apps I want to research a bit closer:

both seem to have voice calling as a feature, I'm not sure if/how they protect IP exposure though.

@0chroma
Copy link
Owner Author

0chroma commented Jul 30, 2024

I'm just gonna linkdump more stuff I need to read into:

Dat Protocol/Dat Rust
Aether
Holochain
RLN

@0chroma
Copy link
Owner Author

0chroma commented Jul 30, 2024

I think for now I'm just gonna be stupid and continue with implementation, libp2p should (fingers crossed) allow us to abstract this problem so that regular TCP/UDP can be swapped out in the future

@0chroma
Copy link
Owner Author

0chroma commented Aug 3, 2024

Another option would be to implement onion-routing at the libp2p layer, providing an alternative to libp2p-kad-dht , example

or just provide a libp2p tor transport

@0chroma 0chroma added the future-work Not important now, maybe later though label Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-work Not important now, maybe later though
Projects
None yet
Development

No branches or pull requests

1 participant