🚀 Element Server Suite 23.11 includes a power-packed Admin Console upgrade.
Set data retention periods, manage on the go with mobile view and supercharge your auditing.
Be in your element with ESS! 🌐
On Wednesday our cofounder & COO Amandine Le Pape will be at Web Summit in Lisbon discussing the need for government CTOs with Andrew Sullivan (President and CEO of Internet Society) & Jane Wakefield (Freelance Senior Technology journalist & Media Consultant BBC).
@debacle @mxmehl @webmink @matrix yes; the work has been going on in the MIMI WG (e.g. https://datatracker.ietf.org/doc/html/draft-ralston-mimi-protocol-01) which has ended up becoming a hybrid of Matrix and MLS-derived work.
@claudius we clearly should have finalised and published the CLA text alongside the announcement. the intention is categorically not to relicense further, but to allow us to sell agpl alternatives fo commercial forks.
@lutindiscret Tchap and Eimis will need to comply with the AGPL or procure an AGPL exception. Neither currently support Element or Matrix financially (Tchap stopped after https://www.nextinpact.com/lebrief/71389/la-dinum-va-voir-son-budget-ampute-40-celui-detalab-plafonne-a-500-000 in April; Eimis never has supported to my knowledge). This is why we are moving to less permissive licensing.
@mxmehl we’re looking at putting a clause in the CLA that guarantees the source will remain published under a OSI license. the need to dual license is to sell AGPL alternatives to third party commercial forks. we are not trying to pull a hashicorp.
@astrojuanlu the CLA is there to let Element sell AGPL exceptions to proprietary forks to try to fund dev. It is not there to allow for relicensing in future.
@f4grx perhaps read the post. the intention is to be able to sell AGPL exceptions to 3rd party commercial forks, in order to fund the underlying dev.
@jabberati @f4grx yeah, if only Matrix worked with existing standards bodies.... oh, wait, what's this? https://datatracker.ietf.org/doc/html/draft-ralston-mimi-protocol-01
@f4grx the only reason for the CLA is not to relicense but to allow dual-licensing for selling AGPL exceptions.
@schmittlauch @serebit @matrix we could have sprouted a proprietary fork of Synapse at any point and stopped developing it as FOSS (due to the Apache license). But we have zero desire to do so. If there's a hack we can use to force us to keep the project FOSS as AGPLv3 then we'll use it. However, we're still going to dual-license in order to try to keep the lights on.
@schmittlauch honestly, we only found about the slint/signal trick via the discussion here today. it looks really interesting, as there is zero desire to pull a hashicorp - we're literally trying to do the opposite.
@serebit @schmittlauch @matrix the whole blog post is explaining that if we don't find a way to get proprietary forks to contribute back to the core project, either by releasing their code as AGPL, or buying a dual license, then core dev from Element is existentially at risk. It's far from ideal, but it's the least worst solution we can find.
@bbhtt @matrix The reason for the shift is so that Element can dual-license the project to commercial forks who currently don't contribute back. This is also the reason for the CLA, to give Element the right to dual-license. The Foundation could have done the same thing, but is not remotely set up for selling licenses, and it'd put the Foundation in competition with Element, which would be nightmarish. Hopefully this is the least worst outcome.
Open, secure and interoperable communication for everyone! 🎉
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!