[deleted]
A roadmap and appeal for help from The Matrix.org Foundation
11–20 of 32 posts
Re: A roadmap and appeal for help from The Matrix.org Foundation
#12> Otherwise, we need to start scaling back programs and staff starting January 2025. They've already done so. 2023 saw a (rather extensive) wave of layoffs, and a reduction in scale. Part of the issue is that Matthew is not the best communicator, which isn't great for fundraising. That being said, Josh isn't off to a strong start, either. Somehow, neither of them managed to spin the Apache -> AGPL move for Synapse as…
I think I don't mind the license change but I'm never contributing code or money to anything with a cla. I have been burned in the past and I have zero interest in contributing anything that will end up in proprietary code.
Conversely I have submitted patches to proprietary, non-OSI-approved-license projects because it is productive for me. If I was not getting paid, sure, but you can have proprietary code and accept community contribution, but you need a CLA.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#13I'm glad to see this roadmap addressed on the financial situation GitHub issue: https://github.com/matrix-org/matrix-spec/issues/571#issueco...
Re: A roadmap and appeal for help from The Matrix.org Foundation
#14Earlier quoted context omitted.
I think I don't mind the license change but I'm never contributing code or money to anything with a cla. I have been burned in the past and I have zero interest in contributing anything that will end up in proprietary code.
Conversely I have submitted patches to proprietary, non-OSI-approved-license projects because it is productive for me . If I was not getting paid, sure, but you can have proprietary code and accept community contribution, but you need a CLA.
Element doesn't need proprietary. If they do, they don't need our money then.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#15I believe Matrix's Now-or-Never Moment has passed.
My last attempt to use Matrox with a group ended in:
- 3 users not receiving notifications on Android
- 2 users regularly not being able to decrypt messages
- No one being able to invite new contacts unless on Desktop
At the same time, Element was working on probably the third app redesign, when the current one... was fine.
These issues crop up, without fail, every time I try to set someone up with Matrix. If If after so many years they still haven't ironed out the basics, they never will.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#16I believe Matrix's Now-or-Never Moment has passed. My last attempt to use Matrox with a group ended in: - 3 users not receiving notifications on Android - 2 users regularly not being able to decrypt messages - No one being able to invite new contacts unless on Desktop At the same time, Element was working on probably the third app redesign, when the current one... was fine. These issues crop up, without fail, every t…
Ive been using matrix private instance for group of nontechnical users for almost a decade now. First with Synapse and now Conduit.
Imho its OK. There are issues with e2ee and well it took most of that decade for Synapse 1.0 stable release…
But if you want private Slack/Discord alternative and run your instance Matrix is still your best choice. Running Conduit with sqlite is pretty easy it. Conduit doesnt yet have all the features but i hope its gonna get there. Element and other clients are pretty good. I am not sure there is better alternative that has threads, image uploads, markdown… all the little stuff people nowdays expect.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#17I believe Matrix's Now-or-Never Moment has passed. My last attempt to use Matrox with a group ended in: - 3 users not receiving notifications on Android - 2 users regularly not being able to decrypt messages - No one being able to invite new contacts unless on Desktop At the same time, Element was working on probably the third app redesign, when the current one... was fine. These issues crop up, without fail, every t…
Almost feels like they bit off more than they could chew with some features. The end to end encryption of group chats is pretty revolutionary, but it's never really felt like it worked, and none of the competitors even try as far as I know. It's just too hard. Being federated probably makes every feature 10x harder to implement.
The bridging feature that they sell also never really worked properly for me. It would go down almost weekly, messages would go missing, get delayed, get reordered, etc. I never felt confident using it and would have to check the actual app to see it come through as expected.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#18I like matrix as much as anyone else around here, and I would like to see it survive and prosper. That being said, if over 60% of the annual “expenses” of your nonprofit goes to “management” covering the salaries of four people who have other full time jobs, you really need to do a better job at managing finances.
as the sibling says, this comment is just plain wrong. the four people funded by the foundation (MD, T&S, standards & advocacy) have no other source of salary than foundation donations.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#19I believe Matrix's Now-or-Never Moment has passed. My last attempt to use Matrox with a group ended in: - 3 users not receiving notifications on Android - 2 users regularly not being able to decrypt messages - No one being able to invite new contacts unless on Desktop At the same time, Element was working on probably the third app redesign, when the current one... was fine. These issues crop up, without fail, every t…
Notifications have gotten better, especially if you use FluffyChat. No clue about the decryption errors.
I find two things way more annoying just because they're so basic. Number one being the fact that replies still look visually wonky quite often and the fact that they're fully RED. Why would they ever use the danger colour for normal things?! The second problem is that when you make a new session it doesn't trust old messages and displays an icon that's utterly useless.
The last one is especially annoying considering how often the clients just corrupt their state and need logging in again. Things like Keybase (RIP) got these things right from the start.
Re: A roadmap and appeal for help from The Matrix.org Foundation
#20> Otherwise, we need to start scaling back programs and staff starting January 2025. They've already done so. 2023 saw a (rather extensive) wave of layoffs, and a reduction in scale. Part of the issue is that Matthew is not the best communicator, which isn't great for fundraising. That being said, Josh isn't off to a strong start, either. Somehow, neither of them managed to spin the Apache -> AGPL move for Synapse as…
Sorry that you feel we haven't done a good job of communicating on this. Personally, I think that https://element.io/blog/synapse-now-lives-at-github-com-elem... was pretty comprehensive in explaining the rationale.
> This offers no protection against Element dropping open source entirely the next time they hit a "budget crisis."
IANAL, but I think you have this completely wrong. The clarification to the Apache CLA was added to ensure that if Element ever distributed contributed code as proprietary (i.e. by providing an AGPL exception to someone allergic to AGPL) then we will also have to distribute that code as FOSS. It is *LITERALLY* stopping us from dropping open source.
> the consistent failures in communication constantly make it feel like things are going to implode
I wonder how much of the "consistent failures in communication" are due to FUD, and how much is due to bad comms in the first place...