How will Matrix be anything other than another stack in the field of silos?
Genuine question. I'm not trying to be combative.
Edit: After doing some more reading through the matrix docs, it seems that the goal is to make an extremely easy to implement/setup endpoint that any 'silo' can easily include. This Matrix endpoint will automagically connect to the Matrix endpoint on other 'silos' to facilitate message transfers.
Is this accurate?
Sure you can write a webapp which uses some combination of long-lived GET, PUT, websockets, HTTP/2 Push etc to 'push' realtime messages around the place, but there's no standard way of doing it; each app makes up its own fragmented and proprietary set of APIs.
So Matrix fixes this by defining a standard HTTP API (which can also be used with other RPC transports if you prefer).
Matrix is an open standard for interoperable, decentralised, real-time communication over IP. It can be used to power Instant Messaging, VoIP/WebRTC signalling, Internet of Things communication - or anywhere you need a standard HTTP API for publishing and subscribing to data whilst tracking the conversation history.
Matrix defines the standard, and provides open source reference implementations of Matrix-compatible Servers, Clients, Client SDKs and Application Services to help you create new communication solutions or extend the capabilities and reach of existing ones.
What is Matrix’s Mission?
Matrix’s initial goal is to fix the problem of fragmented IP communications: letting users message and call each other without having to care what app the other user is on - making it as easy as sending an email.
The longer term goal is for Matrix to act as a generic HTTP messaging and data synchronisation system for the whole web - allowing people, services and devices to easily communicate with each other, empowering users to own and control their data and select the services and vendors they want to use.