logoalt Hacker News

Arathorn10/02/20241 replyview on HN

So we do care about custom emoji, and they are obviously critical for folks looking for an encrypted Discord alternative.

However, right now we're not focusing on building an encrypted Discord alternative but instead a self-hosted WhatsApp (or Teams) replacement for governments: https://element.io/sectors, on the basis that they are the ones paying. Sure, we could have gone after Discord ~5 years ago and launched our own Nitro equivalent, and perhaps we should have. But instead we observed that governments REALLY want to run their own encrypted interoperable comms systems, and we thought that having Matrix used as the backbone for public sector communication would be a good way to prove and fund it sustainably. Ideally we could then use the public sector as a launchpad into other areas - a bit like how email & the web and even the internet spread from DARPA / NSFNet / academic etc to the rest of the world. After all, what better endorsement for Matrix than someone like NATO using it for comms?

As a result, custom emoji are stuck in the middle of the todo list still.

Some of the other features that we've worked on instead have been:

* Making encryption stable. As hilarious as https://www.reddit.com/r/elementchat/comments/1evz3kk/unable... is.

* Make encryption secure - i.e. migrating from the old C/C++ libolm implementation to the rust vodozemac implementation.

* Instant login/sync/launch - i.e. an entirely new sync mechanism.

* Rather than developing 4 different client stacks (js-sdk, ios-sdk, android-sdk and rust-sdk), converge on a single one: matrix-rust-sdk, and make it excellent.

* Rework the core UX to make encryption invisible (rather than full of confusing unactionable warnings and verification nags etc).

* Native Matrix-encrypted scalable voip/video calling.

* Migrating to OpenID Connect for auth, so getting 2FA/MFA etc

* Public sector enterprise features: antivirus, regulatory compliance, secure border gateways, cross-domain gateways, active directory sync, SCIM sync, kubernetes operators, etc. etc.

Now, the plan is to use the govtech business to get back to funding mainstream Matrix uptake. But first we need to be able to fund ourselves to work on it.


Replies

grues-dinner10/02/2024

I see your point, and it sounds like an invidious and existential position to be in and you have my sympathy to be fighting uphill against legacy like that.

Honestly though, I would contest the logic here:

> bit like how email & the web and even the internet spread from DARPA / NSFNet / academic etc to the rest of the world.

It spread because it was useful and revolutionary, not because DARPA specifically used it. Yes there were network effects, but the network effect overlap today between "NATO" and "a friend group hangout" is pretty minimal.

> what better endorsement for Matrix than someone like NATO using it for comms?

Honestly, if all I knew was NATO funded and used it, I'd assume it was enterprise-grade cost-plus shitware 15 years behind the curve, and with zero organisational interest, if not outright hostility, to it being used by anyone without a governmental chequebook and service contract in hand, and steer well clear.

It's OK to write software for NATO and governments for the foreseeable future, but the website still says "communicate with friends, family, communities and co-workers", so you can see why people might think it's still targeted at them and then wonder why it doesn't even provide the baseline of human-interest features people have been getting from other platforms for about a decade.

Not that it helps pays the bills to court Brian Everyman and his Warhammer group chat, I do realise that.

show 1 reply