Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The decentralized WeTransfer

github.com

Post reply on HN
Print view View original

11–20 of 52 posts

Re: The decentralized WeTransfer

#11

Post by alexsicart »

omarchowdhury wrote: post #6

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…

But for example, wetransfer only allow to upload 2GB files, my proposal unlimited and permanent. I believe people don't need to know it uses blockchain...

Re: The decentralized WeTransfer

#13

Post by alexsicart »

mtgx wrote: post #7
monokh wrote: 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.

It's not the same torrents than ipfs, completely different!! https://ipfs.io/

Re: The decentralized WeTransfer

#14

Post by grzm »

alexsicart wrote: post #12
grzm wrote: post #4

Earlier quoted context omitted.

Suggestion: "Decentralized-Cloud IPFS file transfer"

Good one

If you're no longer able to edit the submission title yourself, you can contact the mods via the Contact link in the footer and have them change it for you.

Re: The decentralized WeTransfer

#15

Post by crazygringo »

Joeboy wrote: post #8
omarchowdhury wrote: post #6

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…

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?

Re: The decentralized WeTransfer

#16

Post by monokh »

mtgx wrote: post #7
monokh wrote: 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.

Sure, I guess the difference is, torrents have an inherent mechanism of becoming distributed. Once someone else has a whole/part of the file, they begin seeding immediately (unless stopped of course). In the case of this app, I just receive a download link which is a proxy for pulling something from the network. It would be something else, if the way to get a hold of this file would be through an IPFS node that the user was running.

Re: The decentralized WeTransfer

#17

Post by alexsicart »

omarchowdhury wrote: post #6

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.

Re: The decentralized WeTransfer

#19

Post by alexsicart »

omarchowdhury wrote: post #6

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…

Because this tech, need to be visible to HUMANS if we want to create the next internet.

Re: The decentralized WeTransfer

#20

Post by StavrosK »

monokh wrote: post #16
mtgx wrote: post #7

Earlier quoted context omitted.

> 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.

Sure, I guess the difference is, torrents have an inherent mechanism of becoming distributed. Once someone else has a whole/part of the file, they begin seeding immediately (unless stopped of course). In the case of this app, I just receive a download link which is a proxy for pulling something from the network. It would be something else, if the way to get a hold of this file would be through an IPFS node that the u…

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