Live data from Hacker News

The decentralized WeTransfer

github.com

41–50 of 52 posts

Re: The decentralized WeTransfer

#41
post #30

Bittorrent protocol is decentralized wetransfer right?

Not really, with bittorent sender and receiving peers need to be online at the same time.

It is quite obvious that for any file transfer system to work both sender and receiver have to be online at the same time. One sends the data and the other receives it.

Re: The decentralized WeTransfer

#42

This is the problem I see with decentralized projects. The user experience here, is essentially the same as WeTransfer. The only difference is the underlying technologies. Now, one would have to either blindly trust that the infrastructure is truly decentralized, or have the time and necessary skills to audit the code. And then they'd have to trust that web server is actually hooking up to the code that was just audi…

I believe we should build distributed projects, seems equally to products already people love, but using great tech as ipfs, to have permanent and unlimited files.

Large, unlimited, and permanent files sounds great to the average person. One nitpick I have with the IPFS crowd is the use of the word 'permanent'. They know exactly what it means, but the connotation for the average person is incorrect (persistent data for the latter, permanent address for the former). The marketing problems run deep.

Re: The decentralized WeTransfer

#44

Earlier quoted context omitted.

It would not be inaccurate to consider IPFS as an evolution of the Bittorrent protocol.

Very different protocols!

From the primary IPFS paper [1], which mentions "torrent" 26 times:

"In IPFS, data distribution happens by exchanging blocks with peers using a BitTorrent inspired protocol"

[1] https://github.com/ipfs/ipfs/tree/master/papers/ipfs-cap2pfs

Re: The decentralized WeTransfer

#45
post #8

Earlier quoted context omitted.

Recent reports of google docs arbitrarily removing people's access to their documents seem like pretty good marketing for decentralized solutions.

That was a bug. Are you saying decentralized solutions won't ever have bugs which temporarily prevent people from accessing certain files until the bug gets fixed?

Comparative marketing doesn't hold anything back. Remember the 'opensource/Linux is a cancer ' mantra ?

Re: The decentralized WeTransfer

#46
post #8

Earlier quoted context omitted.

Recent reports of google docs arbitrarily removing people's access to their documents seem like pretty good marketing for decentralized solutions.

That was a bug. Are you saying decentralized solutions won't ever have bugs which temporarily prevent people from accessing certain files until the bug gets fixed?

The bug was "we blocked data as we habitually do, but we reasoned incorrectly on what to block," not "we blocked data by accident, blocking itself is a bug". Same outcome, radically different rationale.

Re: The decentralized WeTransfer

#47
post #7
post #5

I'm trying to figure out how this would be decentralised. As far as I understand, merely hosting something on IPFS doesn't make it decentralised if there is only one node. - Where is my file hosted when I receive it? - Has your server pinned and seeding that file? - Is there a distributed set of nodes that also host it?

> As far as I understand, merely hosting something on IPFS doesn't make it decentralised if there is only one node. Doesn't that apply to torrents, too? If 2 or more people don't own (and share) the exact same content, then of course it's not decentralized.

If you only send a download link to one person, how would there be multiple people sharing the same content?

Re: The decentralized WeTransfer

#48

This is the problem I see with decentralized projects. The user experience here, is essentially the same as WeTransfer. The only difference is the underlying technologies. Now, one would have to either blindly trust that the infrastructure is truly decentralized, or have the time and necessary skills to audit the code. And then they'd have to trust that web server is actually hooking up to the code that was just audi…

how do Dropbox, Google Drive, iCloud Drive, &c. compete? they have similar features, pricing, &c. dex tech doesn't have to be radically different to be competitive, it just has to be good, fast, and have a competitive angle of some kind: perf, price, privacy, &c.

a more interesting angle, imo, is to create an alternative to the GOOG/APPL/MSFT mobile/desktop platforms using free software and dex tech. a lot of the stuff will be the same, people want music, photos, video, social, but I also hope that the p2p architecture will inspire a lot of novel ideas that will only be available inside of our freedom garden.

#heropunch:matrix.org

Re: The decentralized WeTransfer

#49
post #27

Earlier quoted context omitted.

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,…

> 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

Re: The decentralized WeTransfer

#50
post #5

I'm trying to figure out how this would be decentralised. As far as I understand, merely hosting something on IPFS doesn't make it decentralised if there is only one node. - Where is my file hosted when I receive it? - Has your server pinned and seeding that file? - Is there a distributed set of nodes that also host it?

fully distributed
Post reply on HN