3 ms·
I really love every effort in this space and especially if making good use of ipfs, but to give an idea about how far this is from the maturity of lets say sign
by jFriedensreich 6y ago
I really love every effort in this space and especially if making good use of ipfs, but to give an idea about how far this is from the maturity of lets say signal: the more mature parts of ipfs are just starting to become mainstream in the last couple of months. But Berty relies on the very experimantal database orbitdb that relies on the pretty experimental pubsub feature of ipfs that is to my knowledge nowhere near generally usable and scalable. I would consider berty and orbitdb as well as other projects relying on ipfs pubsub all very exciting "future" projects that are just waiting on ipfs to solve the technical challenges and as soon as the ipfs team is ready they will be ready too in a relatively short amount of time. But when that will be is hard to tell, all i know is that pubsub is experimental since early 2017 and my yearly tryouts so far always come to the conclusion that it cannot be widely used yet but will be key to a lot of ipfs applications and could lead to a breakthough for many usecases for ipfs.
- intricatedetail 6y agoWhat are the problems with pubsub? Do they need to invent something not done before or it's just a skill shortage?
- jFriedensreich 6y agoIts a super complex problem to solve, it has been done in some way many times before but not with the exact constraints and tradeoffs that fit well to the rest of the ipfs architecture and that will work on a global scale with unreliable connections and delivery times in the area of ~ a second. Maybe some ipfs dev reads this and can chime in but as far as i understand they are not even really sure about what the correct algorithm for message distribution should be to build on.