Zoom acquired Keybase today.

Keybase helped me to identify a trend in the software industry: using a pretty UI to cover up the disruption of an open ecosystem with a closed, centralized replacement. Keybase seemed cool on the face of it - making encryption easier is a laudible goal, and PGP certainly could use the improvement. But, thanks to Keybase, now I ask different questions upfront.

Beware the Keybase formula:

1. Integrates with an existing, open ecosystem
2. May have open-source clients, but server is closed source and does not federate
3. Pretty UI and good marketing
4. VC funded

Follow

@sir sounds like matrix to me!

@af Really? I'll grant you point 3), but ...

1) a new standard instead of integrating with an existing one

2) server is free code and multiple homeserver implementations exist

4) Matrix Foundation takes no venture capital. New Vector does, so I'd be cautious about using modular.im . But the juiciest data (private chats) is now E2EE by default, so not much datafarming potential. NV don't own any of the "IP" that would allow future acquirers or investors to dominate Matrix development.

@sir

@strypey @sir @af 4) NV owns the developer base and the direction of the project. Is there good reason to consider the MF sufficiently independent from NV?

2) Do multiple implementations actually exist? It was a while ago, but last time I looked, the one non-NV implementation was stalled because the protocol documentation was not up to date with the de facto protocol used by Synapse.

New funding has allowed New Vector to work more on Dendrite, but will that simply replace Synapse as de facto protocol definition, or will NV keep both and the documentation up to date?

@clacke the spec development process for Matrix is managed by the MF, not NV, and happens in the open. So like XEP development at the XMPP Foundation, anyone who is interested can get involved. Not sure if the frequency of bits of the spec being frozen says anything much.

@clacke
> Is there good reason to consider the MF sufficiently independent from NV?

I may be drinking the Kool-aid, but my impression is that NV are aware of the dangers of taking the investor money, and have done everything they can to put MF in charge of the protocol. Not sure who owns the copyrights and trademarks on Riot, Synapse, and Dendrite, but they could be forked at any time by anyone unhappy with the dev direction NV is taking them in.

@sir @af

@clacke

Synapse code being available and Matrix being a federated protocol satisfy @sir 's requirements in point 2). But ...

> Do multiple implementations actually exist

Yes. Not sure exactly what plans NV have for Dendrite and Synapse, but there are also Construct:
github.com/matrix-construct/co

... and Conduit:
git.koesters.xyz/timo/conduit

@af

@clacke Not sure how much progress has been made on getting Conduit and Construct feature-complete and production-ready, but Dendrite is neither yet. A lot of people argue that Synapse isn't really the latter, and even it's developers admit it's a rough-and-ready prototype, which is why they're developing Dendrite.

@sir @af

@strypey @sir @af Yeah they seem to be betting a lot on Dendrite. IIUC, the p2p Riot is a Riot with an embedded Dendrite.
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml