That might explain why Beeper moved away from the fork of the android Element client. I assume they are running a fork of Synapse as the backend as well.
Beeper run a fork of Synapse, but they release their changes under AGPL for the benefit of everyone: https://github.com/beeper/synapse
They moved away from forking Element before we relicensed to AGPL. I rather wish we had licensed Element as copyleft from the outset, as then presumably they would have contributed all the nice Beeper UI back to upstream rather than making a proprietary fork.
Thanks for the clarification, I stand corrected. I really hope they open source their new android client - they are lacking tons of features I'm used to from the element-based android client.
Arathorn|1 year ago
They moved away from forking Element before we relicensed to AGPL. I rather wish we had licensed Element as copyleft from the outset, as then presumably they would have contributed all the nice Beeper UI back to upstream rather than making a proprietary fork.
kldx|1 year ago