Danny O'Bsitting in a room with #IPFS hackers new and old #ipfsconnect
If you don't know #ipfs , it's a peer-to-peer system for finding and then distributing data to and from you, wherever you are, whereever the data is, without unnecessary intermediaries. https://github.com/ipfs/awesome-ipfs
I'm going to nip over to hear the talk on #iroh, which is a new sibling implementation of some parts of the IPFS stack, but if you want to see how IPFS is doing in the browser, follow along with
https://kyledenhartog.com here: https://bit.ly/ipfs-browser-talk
https://kyledenhartog.com here: https://bit.ly/ipfs-browser-talk
So, Iroh is a mobile-centric IPFS-ish system, that emphasizes smooth sync'ing between mobile and local machines (especially when the nodes connectivity goes up and down) https://iroh.computer/
the syncing means that it uses (I think) a different distribution protocol than classic IPFS, but it's still content-addressable. (For instance it uses #blake3 hashing so you can incrementally check the integrity of big files) https://github.com/n0-computer/iroh
This is a theme I see in modern #IPFS usage -- #iroh is optimized for small private networks of a few known devices, rather than one big public network of unknown peers. You see the same setup in https://tryquiet.org/ a Discord-on-IPFS-on-Tor for private groups.
Alaric Snell-Pym@danny ahah, interesting! I was having some trouble with small private IPFS clusters that I partially pinned down to kubo being tuned for global public usage...
@kitten_tech yeah, Kubo ends up being a bit of a super-generalised codebase (one of the reasons why folks tryed to de-emphasise it as the canonical IPFS implementation -- better to have multiple variants speciialising. I think you'd like #iroh! )