If you want to skip right to the good stuff, here's the docs, <a href="https://docs.textile.io/" rel="nofollow">https://docs.textile.io/</a>
Looks neat, I'm a little starved for Go examples in the documentation--I found a couple undocumented example programs in the repo, but I'm not spotting anything in the docs that shows how to do the basics. In fact it took me a bit to even realize there are Go libs, I had originally posted a comment asking for something like ThreadsDB in Go before I spotted the link in the hamburger menu!
I think Textile and its underlying protocols are a step forward that's actually shipping. But it looks a little like an IPFS take on Firestore, but correct me if I'm wrong. But maybe that's because I've been working on too much theory with a distributed protocol of my own for too long rather than getting my hands dirty, ha. Perfect is the enemy of good.
Messing around with some other IPFS-based tooling previously (I think 3Box), I found that the user had to install and be running IPFS in order to view a truly decentralised client application (or there had to be an intermediate webhost that did this for you). This, for me, removed some of the benefits of the decentralised model.<p>Is the Textile toolkit able to operate directly 'on chain' via a standard web browser? Or do visitors still need to install and run executables locally in order for it to work?<p>Sorry if I've inaccurately slandered 3Box here - I am still learning about this space, and I am very excited by the possibilities!
This looks very interesting. It's really nice to see all these decentralized tools popping up now.<p>Are there any WASM based implementation of tools? Would love to see other languages besides JS.<p>One nitpick, Why would they use Slack for their chat?