The decentralized WeTransfer

Post by alexsicart » Tue, Nov 07, 2017, 7:41 PM UTC

monokh wrote: post #27

StavrosK wrote: post #20

Earlier quoted context omitted.

I'm not really sure what you mean. IPFS works just like torrents. As soon as you receive the file, you start "seeding" it.

Yes it does. But I don't believe this app is using any actual seeding mechanisms of IPFS from a user perspective. Which is why i'm asking about where the nodes would be to make this distributed and decentralised. My guess is that the server of this project uploads and "pins" this file in IPFS, in which case it would be no different than a centralised solution. If the server goes down, your file is unaccessible. Also,…

the server never goes down, because is not like TORRENTS!

Post by StavrosK » Tue, Nov 07, 2017, 7:46 PM UTC

alexsicart wrote: post #49

StavrosK wrote: post #32

Earlier quoted context omitted.

> But I don't believe this app is using any actual seeding mechanisms of IPFS from a user perspective I'm not sure what you mean here. Any user can "seed" any IPFS file they want, they don't need anything from this service. > in which case it would be no different than a centralised solution A distributed solution with N=1 isn't the same as a centralized solution. The difference is that distributed solutions can easi…

this project is running an ipfs node in your browser Also, is not like torrents, if disconnect your node, the file disappears!! Read IPFS docs please

> Also, is not like torrents, if disconnect your node, the file disappears

How is it not like torrents? If you're the only seeder and you turn off seeding, does the file not disappear?

> Read IPFS docs please

You're the one who should read them, if you think IPFS is not like torrents.

Re: The decentralized WeTransfer

Re: The decentralized WeTransfer