A rant I posted in the Jupiter Broadcasting Unplugged feedback room
Re 449: about IPFS, I do have some comments/feedback, and some warnings;
IPFS in general was supposed to be a multi-language Thing, however, as of yet, only a golang and a JS version exists. Begin 2020 I was looking to change that, wanting to see python added to the mix (because python is imo a much better language to experiment on), so I started poking at py-libp2p, and through a combination of discussion, talks, and just seeing who or where the maintainers were contributing things, I discovered that IPFS was ran on money, and not the good kind of money.
Py-libp2p (libp2p being a library that was supposed to unify all peer to peer communication in a collaborative way, but is now just a repo merge away from codebase isolation irrelevance) was maintained by ethereum developers, who saw it as a fancy new library to piggyback another client onto, but couldn’t care less for the IPFS usecase itself. That’s kinda fine… if they did not dom