Tenfingers

I know less about I2P, but here is what I understand about the differences and similarities:

#Similarities:

Both encrypt data so that nodes cannot know what they are serving.

Data can be updated, without changing the "link" or address.

Both are FOSS.

#I2P:

Grants access to an anonymous website, hosted by you.

Directly accessible from the WEB.

Does not store content but generates Garlic Routing to your server where the data (your data) is served.

Seems to be more of a routing system that obfuscates the paths between peers, similar to the TOR network with .onion sites.

Even if nothing prevents it, it seems to be made to share mostly one data, a website.

Data is not shared when your PC/server is offline.

I2P is well established.

#Tenfingers:

A distributed, decentralized file system.

Not accessible from the web. Theoretically a plugin could be made to navigate link files in a web browser but it doesn't exist.

EDIT: Web accessibility is underway. A functioning prototype has been built.

Nodes store and serve data. It is not hidden especially, but without a link file, the data is of no use as it is encrypted.

Data is over shared, which ensures redundancy and take-down safety.

Data is shared reciprocally, I share yours because you share mine. This ensures data is actively shared.

Is made to share lots of data.

Data is shared when your PC/server is offline.

Tenfingers is quite new.

.

So in a nutshell, I2P seems to be more a router/communication protocol, and Tenfingers a file-system-like protocol if that makes sense.