Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's more that just the protocol though. TFA links directly to the IPFS Desktop Client, which certainly can have an attitude e.g. if a future update blocks this project. That risk doesn't really exist for any mainstream torrent client.


> TFA links directly to the IPFS Desktop Client

I guess TFA is Teach for America? Doesn't really matter, but anything that is linking to IPFS Desktop could easily link to their own distribution of the client as it's all open source.

And while IPFS Desktop could start blocking content, so could torrent clients, not sure what's different really. They both are just clients for a protocol anyone can write new clients for and both have the risk of adding blocklists and having people abandon the client, so the same risks exists for both of them.


For "TFA", see e.g. https://news.ycombinator.com/item?id=19781756

> so could torrent clients, not sure what's different really

This is precisely why the developers' attitudes do matter. The difference is that the BitTorrent community has a well-established permissive attitude toward copyright violations. This is what gives me a high degree of trust that my next distro update won't bring in any new content blocks. I don't have that high degree of trust in the IPFS developers, given the explicit statements made in favor of upholding existing copyright law.

> anything that is linking to IPFS Desktop could easily link to their own distribution of the client as it's all open source

Sure, but getting people to migrate isn't easy. Look at how many people are still downloading OpenOffice vs LibreOffice, for instance: http://www.openoffice.org/stats/downloads.html




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: