This comment is such an excellent summary of the problem with Element: https://github.com/vector-im/element-web/issues/5891#issuecomment-1620570919
@joepie91 that is an amazing comment thread 🤣🤣🤣
@joepie91 yeah and also the very strong "if something is broken we need to do it right" stuff, but then the right thing takes 2 years and they don't even want to entertain giving users tools to fix common failstates
@eater Yep that's pretty much the issue. Like, I can understand the "we want to do it right" thing, but then they do actually need to *do* it
@joepie91@social.pixie.town imo element isnt really open source, as in they dont really care about contributions like most open source projects, they have these opaque inner workings and randomly block things because they feel like it. i cant wait for the eventual fork.
@j0 I'm not sure that forking Element is the most useful thing, tbh. It would be taking on a lot of technical and organizational debt, with none of the governance influence, and none of the existing team's expertise.
As an external team, it would probably be easier to build something new (that also speaks Matrix), if you intended to fix the many many issues in Element.
@joepie91@social.pixie.town i hope cinny can be that :)
And like, it's not just the notification sound. *So much* stuff in Matrix-land is being held back by this problem!