[0] https://github.com/ipfs/community/blob/master/code-of-conduc...
[0] https://github.com/ipfs/community/blob/master/code-of-conduc...
The CoC you've linked covers the IPFS Community and other Protocol Labs initiatives, it doesn't cover usage of IPFS itself. freeread.org is not bound by that CoC.
What does that have to do with the network? Again, the network nor the protocol currently has nothing in place that describes a "attitude" of being against copyright infringement.
I remember that we (I'm a ex-Protocol Labs employee) used to have plenty of discussions about adding allow/blocklists to the protocol that people could opt-in to, but don't think that was never added (yet?). If it was, I'd understand where you're coming from.
Remember youtube-dl got taken down because it's README file referenced copyrighted material.
It doesn't matter if a tool _could_ be used distribiting copyright material. The tool (and communities) cannot promote anything related to that use case at all.
The same is true with bittorrent. Bittorrent _could_ be used to download copyrighted music and movies, but you won't find a single reference to anything like that use case on their web page because that is illegal: https://www.bittorrent.com/
In fact the bittorrent terms of service says you may not use the tool for any illegal purposes: https://www.bittorrent.com/legal/terms-of-use/
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.
> 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
Everyone has wishes, but wishes aren’t enforceable. It’s the equivalent of “Stop! Or I’ll say stop again!”
> they've
The IPFS Forum - Run by Protocol Labs
> decided to blacklist
Banned discussions around breaking the law on a public internet property owned by a US company.
None of this concerns the protocol itself, which you are free to use for whatever you want, just like HTTP.
Even if so, what can they (the IPFS devs) even do about it?