Arathorn

20 ms·

211.
by Arathorn 1y ago
thanks :) we're still experimenting with whether to replace Element Web's engine with matrix-rust-sdk, or move Element Web's UI components over to the Aurora experiment and build an Element X Web. Given how well the Element-
212.
by Arathorn 1y ago
We're on the case :) https://github.com/matrix-org/matrix-rust-sdk/issues/5350
213.
by Arathorn 1y ago
right, so you are talking about the old legacy Element client, which all those links and the OP are complaining about being clunky/buggy/unappealing. Not the Element X rewrite, which everyone seems to agree is better… but just n
214.
by Arathorn 1y ago
…anti-image-spam protection happens serverside, configured by the room admin. it’s nothing to do with the user’s fault. i’m trying to help fix your problem. can you point me at details so I can investigate?
215.
by Arathorn 1y ago
I'm not sure where the "devs will claim it's my fault if i ask for help" trope is coming from - we really do want Matrix to work :( Do you have a bug report of where this is happening, on what set of clients? A bunch of
216.
by Arathorn 1y ago
are we even talking about the same app? This is literally the first time i’ve heard someone accuse Element X of being clunky, buggy or unappealing - including the original post? The criticism is that it’s not got threads/spaces, sure
217.
by Arathorn 1y ago
We do, in some instances
218.
by Arathorn 1y ago
France has contributed back some code in lieu of money, but it’s a very mixed blessing given we then have to maintain that code, which costs way more in the long term than writing it in the first place. It also actively damages the braintru
219.
by Arathorn 1y ago
This is not correct. Matrix is deliberately asymmetrical - it’s easier to write clients than servers (although that balances has shifted somewhat with E2EE). The reason Dendrite has fallen behind is simply because we couldn’t afford to spli
220.
by Arathorn 1y ago
matrix-bot-sdk does support encryption: https://turt2live.github.io/matrix-bot-sdk/tutorial-encrypti...
221.
by Arathorn 1y ago
in dzaima’s defence they did hit an instance here where messages were effectively dropped - but only because the matrix.org db was so corrupted it incorrectly quarantined them (and even then, they can be flushed through). corruot db is effe
222.
by Arathorn 1y ago
your issue is complaining that matrix-bot-sdk can’t exfiltrate encryption keys which predate it joining a room? this feels like a pretty reasonable limitation. if you really need this, use matrix-rust-sdk with MSC4268 enabled.
223.
by Arathorn 1y ago
Speaking as project lead for Matrix, I obviously feel pretty gutted when someone gives up like this. Doubly so when the straw that broke their back wasn't even a Matrix problem, but really gnarly postgres corruption (see https:/
224.
by Arathorn 1y ago
> The general response from the team was: "Pay money or shut up and accept what we give you". I think you may be unfairly paraphrasing "we don't have enough funding to be able to work on both Element & Element X,
225.
by Arathorn 1y ago
sure, i just genned a new one for you: https://matrix.org/~matthew/mscs.png The trajectory is the same, although obviously it's not ideal that the backlog grows at roughly the same rate as we merge/close them
226.
by Arathorn 1y ago
Element X's performance is great, and the app was built both by product, design & developers (with the performance focus led by dev).
227.
by Arathorn 1y ago
What bit of the protocol docs made you nope out?
228.
by Arathorn 1y ago
The Matrix Foundation is currently massively underfunded (contributing significantly to many of the complaints in this thread, especially around Trust & Safety) and even then losing money. It gets no money from folks like France or NATO
229.
by Arathorn 1y ago
neither YC nor any YC-intermediary is an investor in NV. Instead, you're likely seeing that HN has circuit-breakers against high-temperature threads which turn into pile-ons (whether they're justified or not).
230.
by Arathorn 1y ago
Huge thanks for giving details we can investigate; i've taken a look: * That event is in the matrix.org DB... * ...but it failed authentication checks and got rejected from being added to matrix.org's copy of the room, presumably
231.
by Arathorn 1y ago
> Others who had similar concerns were completely dismissed and attacked by the Element/Matrix admins. This is completely untrue, as per https://news.ycombinator.com/item?id=44599457 . We are VERY aware of the CSAM
232.
by Arathorn 1y ago
The only problem with this statement is that it’s untrue. Element Web/Desktop is 11 years old and has never been rewritten, and while we’re just starting to experiment with the Rust SDK for it, it’s unclear yet whether we migrate the c
233.
by Arathorn 1y ago
this is a good thing, right? spec change proposals is how the spec evolves - they literally turn into PRs to the spec.
234.
by Arathorn 1y ago
It’s depressing to hear that you’ve given up on Element X, given that’s where all the work has been going, including ensuring the encryption is rock solid. Element Call is still webrtc; the fact it’s direct calling to a SFU rather than need
235.
by Arathorn 1y ago
you do understand that schildichat is a relatively light fork of element…?
236.
by Arathorn 1y ago
I think everyone agrees that the classic Element client is slow and has a tonne of tech debt, including bad encryption UX, which is why we rebuilt it as Element X. Web /Desktop is yet to follow, although we’ve started it here: https:&
237.
by Arathorn 1y ago
I’m not aware of any scenarios, including this one, where messages don’t federate (unless the destination server has been unavailable and marked down, obviously).
238.
by Arathorn 1y ago
The corrupt room bug which pushed the OP over the edge was due to a corrupted DB index on matrix.org which caused millions of rows to be incorrectly deleted and was an absolute nightmare to debug and mitigate. You can see some of the story
239.
by Arathorn 1y ago
fwiw these CVEs weren’t reported 6 months ago; they were found during a project which has been running for 6 months.
240.
by Arathorn 1y ago
the spec core team’s employers are: * alexey (red hat) * clokep (simplisafe) * tulir (beeper) * travis (funded by fdn) * uhoreg (element) * richvdh (element) * dbkr (element) * andrew (element) * erik (element) and me from memory andrew &am

More ›