[phyrrus9]

Okay, this sparked an idea to me. We don't really have a way to send large files to each other. So, why dont we all chip in and write a system (somewhat like torrents) in which a user uploads a file to the master node. The master node then breaks up the file into pieces (a maximum size like 2mb will be used per chunk), and then distributes each piece to 3 nodes. When a user wants to download the file, it queries the master node for a list of pieces, and the master node gives out the s/list/count of pieces. After that, the client can query the master node for an individual piece, where the master will then send back (chosen by random) one of the slave nodes containing that piece. Then, the client can query the slave node to download the piece. This way, we can keep speed, save drive space, and even have secure file transfers all with a REALLY simple program.

Anybody else like the idea?

If you guys want to make it a thing, we will need about 50 nodes, and I can host the master.

[Sikom]

How much space or what ever do you need to be a node?

[The Toilet Paper King]

So you want to redesign a perfectly good system (torrents) and make it shit?

How many nodes do you plan to have? 100? 500? 1000? What are the chances that 3 of those nodes containing the desired data will be unavailable? Not to mention the legal implications of it. Sounds like a disaster waiting to happen.

[phyrrus9]

Fun fact, this EXACT system is implemented by the US government.

It isn't actually a torrent system, its a re-implementation of token ring.

@SimPlaysGames the space can be whatever. The protocol supports a full node.

[Sikom]

Fun fact, this EXACT system is implemented by the US government.

It isn't actually a torrent system, its a re-implementation of token ring.

@SimPlaysGames the space can be whatever. The protocol supports a full node.

Do we get anything for this or just for community, and is there any chance that i could get a virus from it?

[Cressi]

It does sound like a nifty piece of system, and I honestly think it could work. Of course, you'll need to convince users it's better than compressing and torrenting, but I do like the sound of it ^^

A question, though; how would you work with encryption? Per node or per package? The master node's security would have to break measures for this to be considered secure, but with a bit of work; it could just happen ^^

A small note: use "URL" instead of "Link" to link text to a specific site.

Spoiler:

<3 XKCD

[phyrrus9]

The cryptosystem would actually be done at the client level, like HTTPS file transfer works. In order to be part of the network, you would need to obtain the correct keys. That would eliminate third party access.

[Cressi]

The cryptosystem would actually be done at the client level, like HTTPS file transfer works. In order to be part of the network, you would need to obtain the correct keys. That would eliminate third party access.

Hmm, sounds fair enough ^^ PM me if you need any help with this, or test drives ^^

[3SidedSquare]

Am I missing something, or is this just Bittorrent Sync?
http://www.getsync.com/

I would still help if we're making an open source alternative though.

[YahwehTheSunGod]

sounds like a cool idea. Lets do it.