Post B2B4v2DLLENbGeKA0u by matrix@mastodon.matrix.org
 (DIR) More posts by matrix@mastodon.matrix.org
 (DIR) Post #B29obNWebTaf9D0BG4 by bagder@mastodon.social
       0 likes, 0 repeats
       
       I really want to love matrix.org but ...
       
 (DIR) Post #B29obOT960NW4cMtQe by matrix@mastodon.matrix.org
       0 likes, 0 repeats
       
       @bagder Matrix isn't a static thing and we keep working away trying to improve it. If you can let us know what's gone wrong (and critically on what client, platform and what server instance) and give us actionable feedback it would be much appreciated.
       
 (DIR) Post #B2AndZ1MvffCaCo4um by chebra@mstdn.io
       0 likes, 0 repeats
       
       @matrix @bagder Half of the problems are caused by matrix.org instance not following the actual matrix protocol specs, or matrix.org instance introducing changes that break compatibility with other (non-synapse) servers or othe (non-element) clients.
       
 (DIR) Post #B2AndZl6BeF8s2CbC4 by matrix@mastodon.matrix.org
       0 likes, 0 repeats
       
       @chebra @bagder while matrix.org does sometimes enable experimental MSCs, they should always be backwards compatible (especially on federation). it doesn’t seem likely that bagder is hitting an edge case where that failed.
       
 (DIR) Post #B2B4v17zNeVDtkoN1s by chebra@mstdn.io
       0 likes, 0 repeats
       
       @matrix should, but often aren't. I'm saying as a long time daily user of matrix. The number of problems caused by this is so high that I totally understand how a non-technical person will end up with a broken account sooner or later, and never come back. Dismissing feedback won't help. Prioritize compatibility. Prioritize stability. Prioritize "users will never see Unable to decrypt". New features don't matter if it keeps breaking.
       
 (DIR) Post #B2B4v2DLLENbGeKA0u by matrix@mastodon.matrix.org
       0 likes, 0 repeats
       
       @chebra not trying to dismiss feedback, but we’re not aware of any problems caused by matrix.org running something incompatible with other clients or servers. what are you actually thinking of? unable to decrypt errors are not to do with matrix.org instance compat (and should be largely gone since sept 2024 as per https://www.youtube.com/watch?v=FHzh2Y7BABQ)