Tenfingers (what is it?)
Tenfingers is a fully decentralised, encrypted, takedown safe, sharing protocol (and implementation) which permits to share data to anyone or just a selected few.
It's FOSS and is based on reciprocal sharing, I share yours because you share mine!
It's like a decentralised cloud file system for anyone to use.
Efforts has been made for ease of setup and usability, particularly on Linux, but you can use it on any modern OS that can run python and pycryptodomex like Windows for example.
More information including quick setup and so on here on the official website.
Didn't find what you looked for? Just make a post and I'll try to answer ASAP.
Valmond
PS. For the daring: Codeberg repo
This sounds interesting. How does it differ from torrents?
Here are some similarities and differences between Tenfingers and Torrents:
#Similarities:
They both use a sort of node swarm, often called a P2P or peer-to-peer network (the Bittorrent network for example).
They permit anyone to share data on the internet by taking data and then distribute a sort of link (torrent, tenfinger link or 10f link).
#Torrents:
With the exception for the creator itself, data are seeded by benevolent nodes.
If the creator stops sharing, the torrent can live on.
Torrents doesn't have to, but are meant to be public.
Torrents seems to be immutable (there are conflicting information about this so I'm not 100% sure, but it seems so, magnet links are immutable).
The torrent ecosystem is built around central trackers. This is not obligatory but seems to be the praxis. E.g. you could share a torrent just with a friend to share some private data. This would be a one shot as torrents are not mutable.
Torrents are made for massive downloads of a specific, often quite large, static data.
#Tenfingers:
With the exception for the creator itself, data are shared by other nodes because of an incentive; reciprocal sharing. This means you can decide how much you want your link shared / how big of a redundancy you want.
When you stop sharing your data, new nodes will not share it and the data will drop from the network because you don't uphold your end of the reciprocal sharing.
You can update the data without changing the tenfinger link, so you can use it as a cloud file system for example.
Tenfingers is made for sharing smaller, dynamic data.
If you have more questions or want more details, just let me know!
Cheers#
Thanks for the detailed response. I'll try it out later this week.
I am still a bit unsure how all this works. Is it comparable to syncthing? Or can you do more with it? I saw something on the tenfingers website about chat applications and the like
Doesn’t Tahoe-LAFS already do this?
Tahoe-LAFS
.
#Similarities:
Free and open source (Tahoe-LAFS is GNU GPL, Tenfingers is GPL-3.0-or-later)
Encrypted
Decentralized, fault-tolerant
Works like a distributed file system
Data is not static, can be changed, updated.
Nodes have no authority (Tahoe-LAFS: Least-Authority File Store, Tenfingers: trust-less nodes)
Proposes Docker images
.
#Tahoe-LAFS:
Seems to be based on benevolent sharing
Can be developed under The Transitive Grace License, which allows owners of the code twelve months to profit from their work before releasing it.
With different centralized frontends data can be accessed with sftp, I2P and more.
As per the official documentation:
So it seems it can be used as a public file system, but was not especially built for it.
.
#Tenfingers:
Is based on reciprocal sharing
FOSS only.
Made for scale in the sense of many users.
.
On a side note; while reciprocal sharing versus benevolent sharing does not seem to be a big difference, it might actually be:
If you decide to share 4TB of data with a 10 times redundancy, in a benevolent cluster it will use up 40TB of space, while in a reciprocal cluster it will add 40TB of space for sharing.
So in a nutshell, there are many similarities but also a couple of differences, Tahoe seems to be more made for personal file systems, Tenfingers is more share oriented.
That doesn’t actually explain anything to me. Is this just an AI bot handling these responses?
Lol I wish :-D
There are a lot of similarities especially on the surface. But Tahoe doesn't seem to be made for large scale usage, as Tenfinger is. Tenfingers use reciprocal sharing (You share a gigabyte, you get a gigabyte back shared for you), while Tahoe uses benevolent sharing (someone else has to pony up with the storage space, or you're just self hosting). There are pros and cons to both.
If there is something unclear, or if you have some specific questions, please do tell and I'll try to explain as clearly as possible.
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.