Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you make a device (say, wireless walkie-talkie) that can communicate with other devices of this type, it is not yet an open standard protocol. It's just your proprietary thingy that you do with some communication properties.

Same thing here. It's a product of one commercial company, which fully decides how it works.

Conduit is not finished, and, given the monolytic nature of matrix protocol (as opposed to XMPP, by the way) it will likely never be finished. Even on it's GitHub page it writes with big big letters: DO NOT RELY ON IT.



> If you make a device (say, wireless walkie-talkie) that can communicate with other devices of this type, it is not yet an open standard protocol. It's just your proprietary thingy that you do with some communication properties.

True, but this isn't the case. The device you are talking about is Element, which uses the protocol. Here you can find the protocol: https://spec.matrix.org/unstable/

It is an open standard.

> Same thing here. It's a product of one commercial company, which fully decides how it works.

You, again, conflate Matrix with Element, which btw. does not fully decide how it works. Read more about that here: https://matrix.org/foundation/

> Conduit is not finished, and, given the monolytic nature of matrix protocol (as opposed to XMPP, by the way) it will likely never be finished. Even on it's GitHub page it writes with big big letters: DO NOT RELY ON IT.

Conduit is a server of a competing entity. I didn't claim it was finished or will ever be finished in the way that there won't be any development any more.


> It is an open standard.

what's it's RFC number? which body does govern the development of this 'protocol'?


Open Standards don't require RFC numbers.

It's governed by the Matrix Foundation, which I have linked before




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: