There’s a magic here in the interoperability and fact that so much hard work has been done to make it ready. The ability for this and IPFS to work together is pretty remarkable in the scope of what can be created.
It could theoretically fail in the IM space and still succeed in the data sharing space. For instance, you could build an Activitypub-like ecosystem on top of it.
THIS is one of the main reasons that I'm such a fan of the matrix protocol. Yes, the chat use case is by far - for now - the most popular direction...but i can envision many other use cases (not just, say, for IoT devices)!
Haven’t tried developing for matrix yet but I’m intrigued by its inertia right now.
Coincidentally, that spec change proposal looks to have been posted exactly one year ago today. Doesn't look like there's anything concrete yet, but still there's obvious opportunities for combining a content-addressable object store API with a distributed content-addressable file system back end.
https://github.com/matrix-org/matrix-doc/blob/travis/msc/ipf...
Matrix was not designed with that goal in mind.
Here's a sneak peek at some of our interfaces:
Even email can carry arbitrary payloads, federates natively and scales extremely well.
Incorrect.
https://github.com/matrix-org/pinecone
It's nowhere near mature/stable, but they are definitely working on it.
Also, P2P overlays already exist in multiple forms.. Yggdrasil, Nebula, Tor, etc. Yet another example of them trying to re-invent the wheel when it isn't even necessary. Tox already does this.