Arathorn

6 ms·

1.
by Arathorn 6d ago
On the point of > speaking of weird: how is it that these models, in a sandbox, with supposedly no way to communicate with other agents, manage to find the same public wikis as a scratch pad for agent communication? It feels somewhat pla
2.
by Arathorn 12d ago
One trick we've been playing with on the Matrix side is figuring out how to tunnel encrypted Matrix over other transports - so you could absolutely use it, layered on top of ATproto spaces, as a way to get E2EE DMLS metadata-protected
3.
by Arathorn 2mo ago
> you don't see the CTO coming to chat about it. Speaking as the CTO at Element (and proj lead for Matrix), i feel like i've spent a bit too much time coming to chat about Matrix on HN over the years ;) That said, I agree that
4.
by Arathorn 2mo ago
I've been keeping a record of the increasingly opinionated vocab it fixates on: * Projection (it seems to love to describe one data structure as a projection of another) * Strand (if some data gets isolated/stuck, it's &quo
5.
by Arathorn 2mo ago
P2P Matrix (and Matrix over DMLS) is back as of a few days ago: see https://arewep2pyet.com and in particular https://arewep2pyet.com/assets/pdf/2026-07-09%20DWebCamp%20P... :)
6.
by Arathorn 2mo ago
This is just the ~8 year old ICAP antivirus scanning system which Element has always had, built for government customer deployments who need antivirus, but implemented for Element X https://github.com/matrix-org/matrix-
7.
by Arathorn 3mo ago
you may be shocked to hear that this is gemini hallucinating; Element (creators of Matrix) has never taken investment from a16z; it must be getting mixed up with a different Element.
8.
by Arathorn 5mo ago
there is a definite irony in switching from being vendorlocked to Signal (open source but closed and locked to a US non-profit) to being vendorlocked to Wire (open source but closed and locked to a German/Swiss for-profit) - talk about
9.
Public sector Matrix deployments in Europe(element.io)
7 points by Arathorn 5mo ago|0 comments
10.
by Arathorn 5mo ago
If you're talking about https://matrix.org/blog/2026/02/analysis-of-reported-issues-... , I'm not entirely sure that characterisation is accurate :)
11.
by Arathorn 5mo ago
It's more that they haven't gone public with it yet, and it's not for us to out them :)
12.
by Arathorn 5mo ago
There's a big gap between lots of orgs using it, and lots of orgs paying for development of it. That said, BWI in Germany is currently funding custom status so it should be coming soon :)
13.
by Arathorn 5mo ago
This is true. We just published a map of it: https://element.io/en/matrix-in-europe
14.
by Arathorn 5mo ago
On the Matrix side, "unexpected" decryption errors got fixed in ~Sept 2024. (There are still a few scenarios where e.g. if you delete your identity keys by logging out of all your clients, you may get "expected" decrypti
15.
by Arathorn 6mo ago
potentially wrapping their own package or distro rather than using something like ESS Community? Or perhaps they left registration open and had abuse problems?
16.
Vulnerabilities in Signal Sealed Sender and Usernames(eprint.iacr.org)
5 points by Arathorn 6mo ago|0 comments
17.
by Arathorn 7mo ago
ooh, that's cool - come tell us about it in matrix.to/#/#twim:matrix.org when it's ready :)
18.
by Arathorn 7mo ago
the main bit of auth which was left unimplemented on matrix-workers was the critical logic which authorizes traffic over federation: https://spec.matrix.org/latest/server-server-api/#authorizat... Auth for clients
19.
by Arathorn 7mo ago
Yes, that's the difference. Loads of Matrix servers have nothing exposed to index, and steer clear of public rooms, and so wouldn't show up on MRS's stats. Whereas I literally select count(*)'d from the destinations tabl
20.
by Arathorn 7mo ago
On the Matrix accessibility side, Element X has improved loads over the years - https://element.io/blog/helping-to-get-everyone-in-their-ele... and https://element.io/blog/element-is-accessible-by-
21.
by Arathorn 7mo ago
The idea of crowdfunding Discordish features for Matrix from disaffected Discorders (e.g. using the premium acct system we've built for matrix.org) has come up a bunch. The problem is more that Element team is seriously stretched (part
22.
by Arathorn 7mo ago
that would be a bit like w3c.org not running a web server on their domain…?
23.
by Arathorn 7mo ago
We're taking it for granted that people do not want to be tracked on the internet, and certainly don't want everyone to have to verify themselves on every site they use. I personally spent ages of time campaigning against the leg
24.
by Arathorn 7mo ago
That post is 2023 vintage and is both outdated and questionable in parts. 19. "media downloads are unauthenticated by default" -> fixed in Jun 2024: https://matrix.org/blog/2024/06/26/sunsett
25.
by Arathorn 7mo ago
I wrote the OP, so to try to clarify: > isn't Matrix based out of the UK and primary hosted instances on AWS in the UK? It doesn't matter what country you run your server in or where your company is based; if you're provid
26.
by Arathorn 7mo ago
...and while we have no choice but implement it on the matrix.org instance, other folks running their own servers are responsible for their own choices.
27.
by Arathorn 7mo ago
https://gitlab.gnome.org/World/Chatty/-/tree/main/src/matrix... might be able to help you?
28.
by Arathorn 7mo ago
The devil is in the details on this. The core concern was that libolm (the obsolete C impl of e2ee in Matrix) used crypto primitives which don’t protect from timing attacks. However, in practice, this was not exploitable: the only way to ex
29.
by Arathorn 7mo ago
cool! would be even cooler to hook it up to https://github.com/matrix-org/matrix-rust-sdk/issues/5350 when it should then just work? matui looks super fun - you should come tell https://matrix.to&#
30.
by Arathorn 7mo ago
this is me working with my users and trying to understand their firsthand experience for myself :)

More ›