element-meta

Every other major client (FluffyChat, Cinny, Nehko, prolly others I’m not aware of) has sticker support, and the ones I mentioned work together seamlessly. Element is cripplingly slow and has an entire drama with a decade-long issue where they continually refuse working commits because they didn’t come from in-house. https://github.com/element-hq/element-meta/issues/339

I really wanted matrix to succeed, but I've completely and entirely given up on it now. State resolution is just a total mess. On the best of days it's a hideously complicated system that sucks crazy resources, and on the worst of days rooms get blown up and bricked. Supposedly it's not as bad as before, but the fact that rooms can get bricked in the first place is bonkers. Just computing the member list of a room is a disaster due to the complex resolution algorithm - I spoke to a homeserver admin once who found that the DB storage space of just the member list can easily reach multiple gigabytes for larger rooms. Also years later, we still don't have custom emojis, user statuses, user bios, invite links etc. - very basic things that literally every messaging platform has. https://github.com/element-hq/element-meta/issues/339 https://

We've posted an update on https://github.com/element-hq/element-meta/issues/2486#issue... - that specific tracking issue had fallen off our radar; sorry.

I sympathize—the web needs a decentralized chat platform. And Matrix seems to be the current best solution. But ignoring real issues with the platform is actively harmful. For example, if you’re active in any FOSS channels, you’re likely to receive spam invites to rooms containing illegal content (with disturbing room images and names that appear on the invite). This has been a known issue for years, and a high visibility issue about it (with responses from Matrix’s managing director) from last summer remains open and largely unaddressed. This issue link is for the Element client, but it contains links to several related proposals for home servers, clients, and the protocol, many of which are still open/completely unresolved. Notably, the MSC related to invite blocking via policy servers or suggestions about ignoring invites via client se

Ugh, yes - i'd made the mental leap that https://github.com/element-hq/element-meta/issues/2700 had finished rolling out, whereas it looks like it's now delayed until October due to having to wait for the ecosystem to catch up. my bad.

> View from 1000 feet: maybe a way to lock a room's users would be interesting? That's a really interesting idea - having immutable memberships could be a good band-aid. The problem is that right now the fact that room membership is typically mutable can be valuable: you add assistants into DMs (human or virtual); you can bridge the DM to other platforms; you can add (benign) audit bots for compliance purposes; you can migrate between Matrix IDs by inviting in your new ID and kicking out the old one; etc. Of course, this same flexibility comes with a risk, and I see the point that it might be better to 'seal' membership if you know this is flexibility you don't want. We'll have a think. > Or, instead, maybe an option to disable forwarding session keys older than the user's room join event, to keep forward secrecy so that a new user does

https://github.com/element-hq/element-meta/issues/339#issuec... is another facet, too.

Right, we haven’t done TLS cert pinning or TOFU yet. Filed as https://github.com/vector-im/element-meta/issues/2073

It's quite disappointing that there's huge ongoing work around reinventing clients from scratch where the basic functionality of not ringing all my devices while I'm using only one of them [1] is still not there (bug open for years), despite it being a pretty simple fix. [1] https://github.com/vector-im/element-meta/issues/360

Scalar (the integration manager) is not open source [1] (though there was some effort to reverse-engineer its protocol [2]); and some of their anti-abuse scripts aren't public [3] [1] https://github.com/vector-im/element-meta/issues/260 [2] https://github.com/turt2live/matrix-dimension/blob/master/do... [3] https://github.com/matrix-org/matrix.org/issues/557