@strypey we are indeed on the same page :)
Discussion
Loading...
Post
@strypey we are indeed on the same page :)
(1/?)
Hi @allpurposemat, it's been pointed out to me that ElementX is now being called a production-ready replacement for "Element Classic", no longer a prototype (despite being wildly incomplete);
https://element.io/blog/deep-dive-into-element-x/
A bunch of your comments make much more sense to me now. You were right. My apologies, both for the misinformation, and the terse exchange that ensued when you were confused by it. #MeaCulpa
(2/?)
> As for the SFU ... Looks like I was wrong about it being proprietary, rather it is an open-core project
My reading of the issue discussion you linked is that a proposed change to the Matrix spec includes a reference to another protocol. It is an open protocol, but not standardised independently of the company who created it. So the concern is the risk of that company enshittifying, and putting future versions of the protocol under a proprietary license (presumably involving patents?).
(3/?)
But as was pointed out in the discussion, the license on already published versions of the protocol spec cannot be revoked. Just like the copyright owners of a free codebase can put future versions under a proprietary license, but can't backdate it to versions released under the free license.
So if the worst were to happen, the last freely-licensed version of the protocol could be forked by the Matrix stewards for their use, whether separately, or integrated into the Matrix spec.
(4/?)
But that's very much a back-of-the-envelope understanding. Once again, I could easily be wrong. Take with grain of salt as appropriate ; )
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled