Why this over I2P? #28
Description
I2P can route any TCP and UDP traffic (so you can use it in-place of public internet)
I2P is mature
I2P has the same MAD (Mutually Assured Destruction) properties as betanet, since blocking I2P fully means blocking all encrypted traffic
And, this is more of a personal issue of mine but:
For a team that develops text editors, resource monitors etc. Isn't it quite anamolus for them to come up with a new IP specification?
From what i can see, these same people also don't have that much of a background in developing such technology.
This is just my conclusion but; I would be wary of this project as a whole; A clear and better alternative already exists, and this project is being authored by a few people that do not have a background in security
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
bageldeveloper commentedon Aug 12, 2025
Agreed, seems like they're trying to just get a quick buck.
cppcooper commentedon Aug 12, 2025
I thought to add perhaps the protocol specific domains, but it seems i2p even provides i2p specific domains. So that rules that out.
Queen12s commentedon Aug 13, 2025
why is this over https???
cppcooper commentedon Aug 14, 2025
https is basically just encrypted http traffic.
I2P hides both content and metadata. It routes traffic through multiple intermediate peers using garlic routing, so neither the sender nor receiver can be easily identified.