speer VS berty

So first I generate a token using the jsonwebtoken crate. This accepts a struct that is serde serializable and deserializeable. After that I construct the Cookie and send it as the response to the request for the '/login' route. You can see my struct here (I named it JWT, but that is not the best name ever, this is the data included in the JWT token): https://github.com/horvbalint/speer/blob/main/backend/src/jwt.rs And then the login route here (line 88): https://github.com/horvbalint/speer/blob/main/backend/src/routes.rs

I just finished rewriting the backend of my side project from Node.js to Rust (actix-web). This is my first 'big' Rust project and I am sure that there are errors/bad practices in my code, so I am looking for some more experienced Rust developers who can review my code and give me feedback. I marked some places in the code, where I am sure that the code can be improved a lot. Here is the repository https://github.com/horvbalint/speer/tree/WIP---backend-Rust-rewrite. The README contains (hopefully) every information needed to get started.

You can try it out here and read more about it and check the repository out here

Not written in Rust, but may be Berty can give you some ideas?

Berty is an open source, secure, private, censorship resilient messaging protocol. Berty is designed to work with NO internet connection. Thanks to Bluetooth LE and mDNS, messages can be securely and privately relayed, peer to peer to create an adhoc network. Of course old fashioned networks still work, and if you’re connected to a “hostile” network that’s being surveilled, the Berty protocol can still operate safely and securely thanks to e2e encryption. Super nice!

Berty: Privacy-first messaging app\ (34 comments)

Well, in fact they have a CLI client ( that I haven't tested ) [1] and their site says they're going to be available also for Mac, Windows and Linux.

https://github.com/berty/berty