When made aware of (near show stopper!!!) issues like those mentioned in this thread the typical reaction from an Element dev is “it works fine for me, make a PR or something”, which forgets that most require concerted efforts to solve, which I’d argue is only realistic with management buy-in. This buy-in seems to be happening (you’re trying to popularize a product, aren’t you??), but so slowly that I don’t see Matrix feasibly replacing proprietary services in this decade. Maybe in the next - for all their faults, they are persistent.
And maybe even already big enough to stick around, with all the public sector buy-in.
I definitely want an open chat standard to succeed and I suppose the best candidate (among astonishingly few!) is Matrix. There’s just still a loooooong road until I can get my friends/acquaintances on it.
> the typical reaction from an Element dev is “it works fine for me, make a PR or something”,
This is false. We check issues which people file and try to reproduce them, and we certainly don't ask randoms to contribute PRs to fix stuff - we'd much much rather fix them ourselves.
Meanwhile, you can see the issue stats at github.com/element-hq/element-x-ios/issues and github.com/element-hq/element-x-android/issues - it's not like we're ignoring or failing to close issues.
I definitely want an open chat standard to succeed and I suppose the best candidate (among astonishingly few!) is Matrix. There’s just still a loooooong road until I can get my friends/acquaintances on it.