matrix-rust-sdk VS pinecone

Compare matrix-rust-sdk vs pinecone and see what are their differences.

matrix-rust-sdk

Matrix Client-Server SDK for Rust (by matrix-org)

pinecone

Peer-to-peer overlay routing for the Matrix ecosystem (by matrix-org)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
matrix-rust-sdk pinecone
13 8
1,036 410
5.5% 0.5%
9.9 3.7
1 day ago 8 months ago
Rust Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

matrix-rust-sdk

Posts with mentions or reviews of matrix-rust-sdk. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-23.
  • Flutter seems to be having bad times internally
    5 projects | news.ycombinator.com | 23 Nov 2023
    Yep, a good example is the element X rewrite

    They use Jetpack on Android

    https://github.com/vector-im/element-x-android

    And SwiftUI on iOS

    https://github.com/vector-im/element-x-ios

    But both use the same underlying Matrix Rust SDK

    https://github.com/matrix-org/matrix-rust-sdk

    So they share the core part of the app between platforms, but everything user facing is native

  • Crux: Cross-platform app development in Rust
    7 projects | news.ycombinator.com | 28 Sep 2023
  • Collaborative WYSIWYG document editor built-on matrix-rust-sdk and matrix-rich-text-editor?
    2 projects | /r/matrixdotorg | 15 Feb 2023
    Hello everyone, I am finally making it to all of the great talks about Matrix from FOSDEM 23, and one thing that seemed like an obvious thing that could be built on some of the new projects works (matrix-rich-text-editor, matrix-rust-sdk) is a collaborative (multi-user, live edits) document tool built ontop of rust. That said, I haven't seen any project doing this yet. Does anyone know of one?
  • Matrix 2.0 — Matthew Hodgson talks about Rust in Element client, Rust SDK, IETF MLS, MIMI and more
    7 projects | /r/rust | 7 Feb 2023
    Another important piece of the ecosystem for which Rust was used is the SDK. This new SDK was used to write the newest mobile client - Element X. The current Element client will also see its cryptography implementation being changed from Javascript to Rust, this was also made possible by the new Rust based SDK.
  • Some key-value storage engines in Rust
    12 projects | /r/rust | 27 Dec 2022
    Let's say I'll switch as soon as they start using Sanakirja. They're partially right in their analysis of Sanakirja, but their comments are more about the lack of expressiveness of the unsafe keyword in Rust than about Sanakirja itself. I'm preparing a blog post about my dream version of unsafe.
  • IRCv3 2022 Spec round-up
    8 projects | news.ycombinator.com | 20 Nov 2022
    >Well I care, that does not mean that you have to care.

    The point I'm making is that the protocol being implement-able by yourself or grabbing a lib from someone else is moot, since you will 9 times out of 10 use a library.

    >Again, look at the lack of client diversity for Matrix and tell me that you do not think that there is at least some correlation in terms of the complexity of the protocol.

    The problem is not client diversity for Matrix - there's plenty of them. The problem is that Matrix is more than displaying a log on a screen, and most of the clients are frankly abysmal and could use a trained UI/UX owner.

    >last I checked it meant using either Python or Go

    The Rust SDK has worked well for me, although I can't state how close it is to Python or Go's libs. That said, I know I'm certainly not the only one using it.

    The Rust lib could be wrapped into other languages (e.g, Ruby) if there's not a good SDK for that language. I don't really consider this to be an issue, especially considering the Rust SDK is maintained by the Matrix org themselves.

    https://github.com/matrix-org/matrix-rust-sdk

    >Add to this that the more mandatory features you have and keep adding

    Don't maintain your own bespoke library and you won't have to. :)

    >But I am not going to behave as if images, reactions, code blocks, threads, end-to-end encryption, voice calls, video calls, etc. do not come at a cost.

    They do come at a cost, but that's the price of admission for what people expect from modern chat systems. I'd rather live in 2022 than 2004, and I grew up on IRC.

  • Back to School: Free Rust Courses
    7 projects | /r/rust | 27 Aug 2022
    I'm not entirely sure what I plan to use Rust with at the moment, however my first project so far has been to write a Matrix bot using the matrix-rust-sdk library :)
  • GTK4 Matrix Client
    6 projects | news.ycombinator.com | 10 Apr 2022
    Just for everyone else reading, the modern Matrix Rust stack referred to here is the matrix-rust-sdk: https://github.com/matrix-org/matrix-rust-sdk
  • E2EE vulnerability in multiple Matrix clients
    8 projects | news.ycombinator.com | 13 Sep 2021
    The current way we're approaching this is to split the reference E2EE implementation into its own rust crate (https://github.com/matrix-org/matrix-rust-sdk/tree/master/ma...) which can be used with any SDK (e.g. we're almost finished embedding it into the Kotlin matrix-android-sdk2 client)

    Separately, there's also the overall matrix-rust-sdk https://github.com/matrix-org/matrix-rust-sdk for clients to use as a "full fat" Matrix client SDK - as used by Fractal Next (https://gitlab.gnome.org/GNOME/fractal/-/tree/fractal-next) etc. We might end up using this in Element too in future (especially in Element iOS, where a Swift UI + matrix-rust-sdk backend could be quite a cute next generation architecture).

    So while the first generation reference Matrix SDKs (matrix-js-sdk, matrix-ios-sdk and matrix-android-sdk) were completely independent implementations, each with their own bugs and increased audit surface, we're hoping that matrix-rust-sdk will simplify this a lot in future.

  • Announcing Conduit Beta (Matrix chat server)
    2 projects | /r/rust | 1 Sep 2021
    If you want to (re)write an appservice in Rust, have a look at https://github.com/matrix-org/matrix-rust-sdk/issues/228.

pinecone

Posts with mentions or reviews of pinecone. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-31.
  • Meshtastic: An open source, off-grid, decentralized, mesh network
    8 projects | news.ycombinator.com | 31 Dec 2023
    Do you have any examples of their mobility event handling? I'm reading the documentation for Pinecone and don't see much. Even Pinecone says Yggdrasil's spanning tree isn't good enough: "However, the spanning tree topology alone is not a suitable routing scheme for highly dynamic networks." [0]

    I'm reading that as why Pinecone has the virtual snake topology. But they define that as a public key-based routing, which doesn't take into account optimal routing in the network. Nodes are ordered by public key [1]

    [0] https://github.com/matrix-org/pinecone#does-pinecone-work-on...

    [1] https://matrix-org.github.io/pinecone/snake

    8 projects | news.ycombinator.com | 31 Dec 2023
  • The AT protocol is the most obtuse crock of s*
    9 projects | news.ycombinator.com | 9 May 2023
    AT proto has some significant similarities to Matrix:

    * Both are work by self-authenticating git-style replication of Merkle trees/DAGs

    * Both define strict data schemas for extensible sets of events (Matrix uses JSON schema - https://github.com/matrix-org/matrix-spec/tree/main/data/eve... and OpenAPI; AT uses Lexicons)

    * Both use HTTPS for client-server and server-server traffic by default.

    * Both are focused on decentralised composable reputation - e.g. https://matrix.org/blog/2020/10/19/combating-abuse-in-matrix... on the Matrix side, or https://paulfrazee.medium.com/the-anti-parler-principles-for... on the bluesky side, etc.

    * Both are designed as big-world communication networks. You don't have the server balkanisation that affects ActivityPub.

    * Both eschew cryptocurrency systems and incentives.

    There are some significant differences too:

    * Matrix aspires to be the secure communication layer for the open web.

    * AT aspires (i think) to be an open decentralised social networking protocol for the internet.

    * AT has portable identity by default. We've been working on this on Matrix (e.g. MSC1228 - https://github.com/matrix-org/matrix-spec-proposals/pull/122... and MSC2787 - https://github.com/matrix-org/matrix-spec-proposals/blob/nei...) and have a new MSC (and implementation on Dendrite) in progress right now which combines the best bits of MSC1228 & MSC2787 into something concrete, at last. In fact the proto-MSC is due to emerge today.

    * AT is proposing a asymmetrical federation architecture where user data is stored on Personal Data Servers (PDS), but indexing/fan-out/etc is done by Big Graph Servers (BGS). Matrix is symmetrical and by default federates full-mesh between all servers participating in a conversation, which on one hand is arguably better from a self-sovereignty and resilience perspective - but empirically has created headaches where an underpowered server joins some massive public chatroom and then melts. Matrix has improved this by steady optimisation of both protocol and implementation (i.e. adding lazy loading everywhere - e.g. https://matrix-org.github.io/synapse/latest/development/syna...), but formalising an asymmetrical architecture is an interesting different approach :)

    * AT is (today) focused on for public conversations (e.g. prioritising big-world search and indexing etc), whereas Matrix focuses both on private and public communication - whether that's public chatrooms with 100K users over 10K servers, or private encrypted group conversations. For instance, one of Matrix's big novelties is decentralised access control without finality (https://matrix.org/blog/2020/06/16/matrix-decomposition-an-i...) in order to enforce access control for private conversations.

    * Matrix also provides end-to-end encryption for private conversations by default, today via Double Ratchet (Olm/Megolm) and in the nearish future MLS (https://arewemlsyet.com). We're also starting to work on post quantum crypto.

    * Matrix is obviously ~7 years older, and has many more use cases fleshed out - whether that's native VoIP/Video a la Element Call (https://element.io/blog/introducing-native-matrix-voip-with-...) or virtual worlds like Third Room (https://thirdroom.io) or shared whiteboarding (https://github.com/toger5/TheBoard) etc.

    * AT's lexicon approach looks to be a more modular to extend the protocol than Matrix's extensible event schemas - in that AT lexicons include both RPC definitions as well as the schemas for the underlying datatypes, whereas in Matrix the OpenAPI evolves separately to the message schemas.

    * AT uses IPLD; Matrix uses Canonical JSON (for now)

    * Matrix is perhaps more sophisticated on auth, in that we're switching to OpenID Connect for all authentication (and so get things like passkeys and MFA for free): https://areweoidcyet.com

    * Matrix has an open governance model with >50% of spec proposals coming from the wider community these days: https://spec.matrix.org/proposals

    * AT has done a much better job of getting mainstream uptake so far, perhaps thanks to building a flagship app from day one (before even finishing or opening up the protocol) - whereas Element coming relatively late to the picture has meant that Element development has been constantly slowed by dealing with existing protocol considerations (and even then we've had constant complaints about Element being too influential in driving Matrix development).

    * AT backs up all your personal data on your client (space allowing), to aid portability, whereas Matrix is typically thin-client.

    * Architecturally, Matrix is increasingly experimenting with a hybrid P2P model (https://arewep2pyet.com) as our long-term solution - which effectively would end up with all your data being synced to your client. I'd assume bluesky is consciously avoiding P2P having been overextended on previous adventures with DAT/hypercore: https://github.com/beakerbrowser/beaker/blob/master/archive-.... Whereas we're playing the long game to slowly converge on P2P, even if that means building our own overlay networks etc: https://github.com/matrix-org/pinecone

    I'm sure there are a bunch of other differences, but these are the ones which pop to the top of my head, plus I'm far from an expert in AT protocol.

    It's worth noting that in the early days of bluesky, the Matrix team built out Cerulean (https://matrix.org/blog/2020/12/18/introducing-cerulean) as a demonstration to the bluesky team of how you could build big-world microblogging on top of Matrix, and that Matrix is not just for chat. We demoed it to Jack and Parag, but they opted to fund something entirely new in the form of AT proto. I'm guessing that the factors that went into this were: a) wanting to be able to optimise the architecture purely for social networking (although it's ironic that ATproto has ended up pretty generic too, similar to Matrix), b) wanting to be able to control the strategy and not have to follow Matrix's open governance model, c) wanting to create something new :)

    From the Matrix side; we keep in touch with the bluesky team and wish them the best, and it's super depressing to see folks from ActivityPub and Nostr throwing their toys in this manner. It reminds me of the unpleasant behaviour we see from certain XMPP folks who resent the existence of Matrix (e.g. https://news.ycombinator.com/item?id=35874291). The reality is that the 'enemy' here, if anyone, are the centralised communication/social platforms - not other decentralisation projects. And even the centralised platforms have the option of seeing the light and becoming decentralised one day if we play our parts well.

    What would be really cool, from my perspective, would be if Matrix ended up being able to help out with the private communication use cases for AT proto - as we obviously have a tonne of prior art now for efficient & audited E2EE private comms and decentralised access control. Moreover, I /think/ the lexicon approach in AT proto could let Matrix itself be expressed as an AT proto lexicon - providing interop with existing Matrix rooms (at least semantically), and supporting existing Matrix clients/SDKs, while using AT proto's ID model and storing data in PDSes etc. Coincidentally, this matches work we've been doing on the Matrix side as part of the MIMI IETF working group to figure out how to layer Matrix on top of other existing protocols: e.g. https://datatracker.ietf.org/doc/draft-ralston-mimi-matrix-t... and https://datatracker.ietf.org/doc/draft-ralston-mimi-matrix-m... - and if I had infinite time right now I'd certainly be trying to map Matrix's CS & SS APIs onto an AT proto lexicon to see what it looks like.

    TL;DR: I think AT proto is cool, and I wish that open projects saw each other as fellow travellers rather than competitors.

  • Pinecone raises $100M Series B
    6 projects | news.ycombinator.com | 27 Apr 2023
  • Matrix 2.0 — Matthew Hodgson talks about Rust in Element client, Rust SDK, IETF MLS, MIMI and more
    7 projects | /r/rust | 7 Feb 2023
    Pinecone, which is an experimental overlay routing protocol used by P2P Matrix. It and Dendrite are extremely important to P2P Matrix.
  • Ask HN: What's in Networking?
    2 projects | news.ycombinator.com | 13 Jul 2022
    I'm excited about P2P/decentralized/distributed overlay networks. Still catching up so would be grateful for tips on resources.

    Pinecone[0][1], newer initiative made by former Yggdrasil[2] maker(s).

    CJDNS[3].

    AIUI CJDNS relies on intermediary high-uptime discoverable router nodes which is what is motivating Pinecone. POKT[4][5] to CJDNS seems like what Filecoin is to IPFS.

    I'm yet to get around to doing the groundwork of grokking more established solutions like B.A.T.M.A.N. and how all these pieces fit together,

    [0]: https://fosdem.org/2022/schedule/event/matrix_p2p_pinecone/

    [1]: https://github.com/matrix-org/pinecone

    [2]: https://yggdrasil-network.github.io/

    [3]: https://github.com/cjdelisle/cjdns/

    [4]: https://www.pokt.network/

    [5]: https://piped.kavin.rocks/watch?v=-xgRUAA_p5E

  • Make the Internet Yours Again with an Instant Mesh Network
    2 projects | news.ycombinator.com | 9 Jan 2022
  • Element raises $30M to boost Matrix
    18 projects | news.ycombinator.com | 27 Jul 2021

What are some alternatives?

When comparing matrix-rust-sdk and pinecone you can also consider the following projects:

pgvector - Open-source vector similarity search for Postgres

conduit

element-android - A glossy Matrix collaboration client for Android.

threema-android - Threema App for Android.

gomuks - A terminal based Matrix client written in Go.

yggdrasil-go - An experiment in scalable routing as an encrypted IPv6 overlay network

DiskANN - Graph-structured Indices for Scalable, Fast, Fresh and Filtered Approximate Nearest Neighbor Search

weechat-matrix-rs - Rust rewrite of the python weechat-matrix script.

matrix.to - A simple stateless privacy-protecting URL redirecting service for Matrix

Ruma - A set of Rust crates for interacting with the Matrix chat network.

matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker

matterbridge - bridge between mattermost, IRC, gitter, xmpp, slack, discord, telegram, rocketchat, twitch, ssh-chat, zulip, whatsapp, keybase, matrix, microsoft teams, nextcloud, mumble, vk and more with REST API (mattermost not required!)