3 ms·

> "But the only thing that can be done is work on an actual protocol that will solve these problems." What about the Matrix protocol (referenced in other comme

> "But the only thing that can be done is work on an actual protocol that will solve these problems." What about the Matrix protocol (referenced in other comments made in this discussion)?

scrollaway 11y ago
I am following it from afar. I don't see how it'll gain traction, ever, though. The marketing problem is one devs don't like to solve, but it has to be solved.
- Arathorn 11y ago
  The plan for marketing it is: * Ensure there are glossy Matrix-native clients out there with a Slack-equivalent level of good UI and UX (e.g. http://vector.im/beta http://vector.im/beta) * Build bridges to federate together as many different protocols as possible. This includes IRC, Slack, XMPP, SIP, Lync, Verto, Respoke etc. We're trying to make this as easy as possible by providing some high level building blocks like http://github.com/matrix-org/matrix-appservice-bridge http://github.com/matrix-org/matrix-appservice-bridge. This hopefully will make it easy for others to bridge themselves into Matrix once we have critical mass. * Release a stable version of actual Matrix standard itself, keeping it as simple but capable as possible. (Right now it's not frozen, and it's still in beta) * Provide a really capable reference server implementation. (The current one, synapse, is a good starting point and works well for experimenting with Matrix, but we still have work to do on performance and scalability). * Run around the world encourage existing projects/networks/solutions/developers to get involved and defragment their comms - a bit like the early internet guys had to do with defragmenting email. It's obviously hugely ambitious, but we actually have some good traction already (despite still being in beta). Hopefully the trend will continue! [Disclaimer: i work on it]
  - scrollaway 11y ago
    Best of luck! I'll do my best to support you.
- heavenlyhash 11y ago
  I got my mother to use Matrix. She's a smart cookie, granted. But she's not a developer. I couldn't reasonably get her to use IRC. I couldn't get her to use XMPP. I couldn't get her to use Facebook chat. (Moral reasons, there, mostly.) She could get started using Matrix in a single sitting. We're still using it to communicate. Anecdata? Absolutely. With a dash of emotional appeal, even -- the worst kind of anecdata! Still: true. So, while Matrix may not have a million dollar marketing budget in play... there's reasonable hope that the ease-of-use requirement for mass adoption is well on its way.

> "But the only thing that can be done is work on an actual protocol that will solve these problems." What about the Matrix protocol (referenced in other comments made in this discussion)?

scrollaway 11y ago

I am following it from afar. I don't see how it'll gain traction, ever, though. The marketing problem is one devs don't like to solve, but it has to be solved.

Arathorn 11y ago
The plan for marketing it is: * Ensure there are glossy Matrix-native clients out there with a Slack-equivalent level of good UI and UX (e.g. http://vector.im/beta http://vector.im/beta) * Build bridges to federate together as many different protocols as possible. This includes IRC, Slack, XMPP, SIP, Lync, Verto, Respoke etc. We're trying to make this as easy as possible by providing some high level building blocks like http://github.com/matrix-org/matrix-appservice-bridge http://github.com/matrix-org/matrix-appservice-bridge. This hopefully will make it easy for others to bridge themselves into Matrix once we have critical mass. * Release a stable version of actual Matrix standard itself, keeping it as simple but capable as possible. (Right now it's not frozen, and it's still in beta) * Provide a really capable reference server implementation. (The current one, synapse, is a good starting point and works well for experimenting with Matrix, but we still have work to do on performance and scalability). * Run around the world encourage existing projects/networks/solutions/developers to get involved and defragment their comms - a bit like the early internet guys had to do with defragmenting email. It's obviously hugely ambitious, but we actually have some good traction already (despite still being in beta). Hopefully the trend will continue! [Disclaimer: i work on it]
- scrollaway 11y ago
  Best of luck! I'll do my best to support you.
heavenlyhash 11y ago
I got my mother to use Matrix. She's a smart cookie, granted. But she's not a developer. I couldn't reasonably get her to use IRC. I couldn't get her to use XMPP. I couldn't get her to use Facebook chat. (Moral reasons, there, mostly.) She could get started using Matrix in a single sitting. We're still using it to communicate. Anecdata? Absolutely. With a dash of emotional appeal, even -- the worst kind of anecdata! Still: true. So, while Matrix may not have a million dollar marketing budget in play... there's reasonable hope that the ease-of-use requirement for mass adoption is well on its way.